Client Support
Showing results for 
Search instead for 
Do you mean 

Urgent ...? After the upgrade, a very important Internal Location changed to External

Frequent Advisor

Urgent ...? After the upgrade, a very important Internal Location changed to External

[ Edited ]

before upgrade : HP TRIM 7.1.1828 Win 7 , MS Office 2010, SQL 2008-R2

Now HP trim 7.3.3.5645 , Win 7 , MS Office 2010, SQL 2008-R2

 

So

Yes, the Organisation location suddenly changed from Internal to external.

 

The speculation is that the very important Organisation location changed from INTERNAL to the External just after the recent TRIM upgrade, causing access issues for a certain record types..... All users belonging to that organisation were not being able to use the particular record type.

in the LAST DATE Updated column, for that Location the date is oldish... June 2013 .... Not 2-3 weeks or yesterday ...

What could be the reason of this hapening and is it safe to make the organisation Location back to Internal?

Is it safe to simply make it Internal again, during the business hours?

Some test environment and Dev environment show this Organisation as the Internal some as external .

Thanks

 

4 REPLIES
HPE Expert

Re: Urgent ...? After the upgrade, a very important Internal Location changed to External

Unsure as to why the location changed, I would assume that it would be safe to swap back, in fact it will be required.

 

It might be something that you would want to test first before attempting in production.

 

If you get stuck, log a support case. It will be better to keep track of this issue.

**Any opinions expressed in this forum are my own personal opinion and should not be interpreted as an official statement on behalf of Hewlett Packard Enterprise**
Honored Contributor

Re: Urgent ...? After the upgrade, a very important Internal Location changed to External

Are you able to replicate the issue with a copy of the pre-upgrade database?

If you go through the same schema upgrade, does the same location change?

Did any others change?

 

If it's just a single location that changed, no others, and you can't replicate again, I can only suggest that it was changed via some other user interaction and not the upgrade process itself.

 



::::::::::::::::::::::
NOT A HP EMPLOYEE
::::::::::::::::::::::

Kapish.com.au
Frequent Advisor

Re: Urgent ...? After the upgrade, a very important Internal Location changed to External

Thanks guys,

All test machines; all test servers show that Organisation now as External. (I checked)

Only one of development servers shows it at Internal ( the proper one).

 

Not sure wheter this change hapened straight after the upgrade or just recently... (A user that reported an issue sent an e-mail to us on Wednesday, 2 weeks after the upgrade)

 

If you guys can remember , we did ahve a similar issue with the TRIMPORT.exe (when importing 10,000 Organisation Locations, external ones) making external locations Internal (if some do not exist, they would be created but by default as the INTERNAL, although in the importing file/document we clearly stated that all 10,000 locations must be EXTERNAL)

 

Any connection with this or ?

Anyway, the problematic Location Organisation is now back as Internal , no issues reported ...yet...

Thanks

 

 

Honored Contributor

Re: Urgent ...? After the upgrade, a very important Internal Location changed to External

Thanks for the update.

 

It definitely sounds like an issue outside of the upgrade process.
Unless you trawl through your Audit Logs, it would be hard to say what changed it.



::::::::::::::::::::::
NOT A HP EMPLOYEE
::::::::::::::::::::::

Kapish.com.au