I’ve never been able to migrate identity objects using SP Config or Configuration Hub. I’ve tried looking around, but any guidance I can find is either irrelevant to the issues I’m seeing, or too vague to be of any practical use. I’m hoping somebody here might help me see what I’m doing wrong. To be clear - I’m not talking about Identity Profiles yet, just the IDENTITY_OBJECT_CONFIG.
I get the same error in Configuration Hub and using SP Config API’s directly:
“An error occurred while importing Identity Object Config with name ‘Identity’”
There is no other information provided. There is no attribute synchronization enabled on any source in either environment and I have confirmed that the “attributeTargets” nodes of the json are all null.
I have attempted to update the “ruleRef” manually to match the id value in the target environment, but that has not changed the error. And I even tried to update the Identity Object id to match the production id, but that didn’t help either.
If you have successfully migrated Identity Attributes between environments using Configuration Hub or SP Config please provide some guidance on how you have done so.
Are you saying that you have gotten it working that way?
I’m a bit skeptical because the discussion you linked to very explicitly says that you need to migrate IDENTITY_OBJECT_CONFIG before IDENTITY_PROFILE configs. I can’t see how trying them both at the same time would make things better.
Unsurprisingly, attempting to migrate both at the same time did not work. This time I got the error message: exceptionMessage": “Identity Object Config attribute(s) referenced by Identity Profile attribute mapping(s) “[activeDirectoryOu, category, categoryCode, departmentCode, emcOfDepartment, employeeStatus, employeeType, fileNumber, flsaCode, flsaDescription, hireDate, isTestUser, officerClassCode, officerTitleDescription, positionStartDate, positionStatus, positionID, preferredLastName, rehireDate, titleCode]” not found”
This indicates that the Identity Object config needs to be migrated first, which is what I’m actually trying to do. Identity Profiles are not a factor here and I’m not going further down that path unless you can provide a reasonable explanation for how it will lead to a solution.
Hey @KevinHarrington I have recently faced this issue when trying to migrate the IDENTITY_OBJECT config using Config Hub.
I have tried many times repeatedly, and there is no luck importing; every time I faced the same error. So I have done the below step first and then imported the identity object config; it works.
Created all Identity Attributes in existing IDP (IdentityNow Admins)
Don’t map the attributes
Next try to import the identity object; it works for me.
If you want, you can add the IDP as well during the import.
So I’m clear, all this migrates is whether the attributes are available for correlation then, right? You’re basically doing 90% of the work manually and the migration tool just finishes off the final bit.
Migration carries over the Identity Object Config metadata, provided the source schema, account attributes, source-specific configurations already exist in the target tenant. So, most prerequisite setup is still done manually. Then the migration helps transfer the final Identity Object Config layer rather than recreating the entire Source Configuration.
Hey @KevinHarrington , had this issue recently. Here’s the background and soln:
The Cloud Rule IDs in the IDENTITY_OBJECT_CONFIG are not being automatically resolved, e.g. for Cloud Promote Identity Attribute, Cloud Calculate Identity Status, and Cloud Calculate Internal Identity Status
As a result, deploying through config hub will show the error An error occurred while importing Identity Object Config with name ‘Identity’
Solution:
Pull the Draft object into VS Code or Notepad++
Do a find/replace on all rule IDs to replace the draft ID with the ‘live’ ID, e.g., the Sandbox Rule ID with the PROD rule ID
Deploy again
This fixed for me in multiple tenants - hope it helps
