Home › Forums › implementation › Implementation discussion ›

Best way to handle roles in 1.7 to 1.9 upgrade

Submitted by Guest on Sun, 23/04/2017 - 07:21
in

What is the optimum way to handle roles & authorities in a 1.7 to 1.9 upgrade?

I did the standard database migration 1.7-->1.8-->1.9 and this added in the various new authorities.

After firing up the system, I realised that the 1.7 system had previously had almost no authorities & roles - so I ran dataload -f ..\import\data\roles.xml

This gave me the Base & Logistics roles but also duplicated the authorities that the migration had created.

I suspect that the proper procedure is to run dataload prior to doing the database migration.

[Note that I am working on a test system, and the actual migration of the production system is planned for next week and I would like to understand what I should have done prior to doing the real migration.]

Regards, Tim G

‹ Amazon Linux rather than Ubuntu? remove sms character limit ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Re: Best way to handle roles in 1.7 to 1.9 upgrade

Submitted by tanderson on Mon, 24/04/2017 - 15:58.

Loading the roles prior to the migration would be the best approach.

Re: Best way to handle roles in 1.7 to 1.9 upgrade

Submitted by tgething (not verified) on Mon, 01/05/2017 - 07:59.

I ended up loading the 1.7 roles prior to migration and then checking things after migration. I had to manually add the manufacturing batch stuff to the Stock Control role. [ie I compared the authorites given the the Stock Control role in the 1.9 roles.xml file with what was set in the system and added what was missing.] The Base role seemed OK.

Regards, Tim G

Syndicate content