Pages

Monday, April 8, 2019

Workaround to new error during import of security setup

As a new feature to the security setup export and import, Microsoft has added information about objects being disabled/deleted, so the receiving system is able to pick that up too.

But if you both update an object and then disable it, you have created a combination of actions that cannot be imported. This is the error you'll get during import:


The technical reason reason is that the import deals with deleting/disabling objects before it deals with the updates. So when it gets to the update part, it cannot find the object.

The workaround is to pull out your best scissor software and cut out the update part of the XML. Here is an example where I have tried this with the TestEssentialsRole role:


Surprisingly to me is that this, according to MS support, works exactly as designed.

No comments: