Importing a large exported Permission Set XML file (to clone it) results in a new permission set that's only partially granted — some database objects end up not granted at all, with an error referencing something like SYS.ALL_TABLES appearing at the end of the import, and the freshly cloned permission set exports noticeably smaller than the file that was imported. What's going on, and how is this worked around?

All FAQ questions / Security and access

Answer

This points to the import process not completing cleanly in one pass for very large permission sets (possibly related to file size or the import's own runtime). A workaround that's worked in practice: run the XML import once to create the initial (incomplete) permission set, then re-run the same import again choosing the 'Merge' option instead of a fresh import, repeating Merge-mode imports until the only errors reported are ones you'd genuinely expect (like references to projections that don't exist in this particular environment). Each subsequent Merge-mode import runs noticeably faster than the original import, and repeating it until only expected errors remain has produced a clean, fully-granted clone of the source permission set.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Security and access questions