Security "Reset" When Prod is Copied to Dev
Is it normal for certain security settings to be "reset" when a copy of production is made to dev?
Every time we make a copy of production into the development environment certain security fields w...
Forum Discussion
T_Kress is on the right track - the problem is that the Framework database in your 2 environments are not the same (and that is normal). The problem though is that the metadata security groups are stored in the database using their unique ids not the name and while the security groups might be in both environments, they have different unique ids. The way to solve this is to update the security groups in DEV with the PRD groups but you need to select 'Extract Unique IDs':
That will load/update the security groups using the same unique IDs as PRD.
It might also mess up the user security assignments in DEV. So the steps you need are:
- extract DEV security without Unique IDs
- extract PRD security with unique IDs
- load PRD security extract into DEV
- load DEV security extract into DEV to reset the user assignments
I think that will do it but I haven't tested it.
Thanks Marcus. I tried this but got an error that the unique ID cannot be changed (for security groups that already existed in DEV with another unique ID). So I tried deleting a group in DEV then loaded that group from PROD with unique ID but also got an error that the unique ID was being used by another item. I will open a ticket with OS support to see if they can help me further.