Hello,
When migrating access profiles via Config Hub, certain entitlement references will not resolve due to multiple entitlements having the same name, which is expected in this environment. The reference errors in the draft will look like this:
13 matching references found for object type ENTITLEMENT using url entitlements-v3/entitlements?ignoreDataSegment=true with value xyz. Unable to resolve multiple references.
Unable to resolve reference for object [type: ENTITLEMENT, id: 000, name: xyz] at path $[‘entitlements’][0] in object [type: ACCESS_PROFILE, id: 111, name: abc]
We created an object mapping to replace entitlement id with the correct one in the target, and that works as expected, we can see the id being replaced and we can see that the object mapping was utilized.
However, the issue is that the reference errors still remain in the draft even though the entitlement id got replaced. Is this an expected behavior? I would expect the reference error to not show up since the object mapping helped resolve it. This makes it inconvenient and unworkable having to go down a list of dozens of access profiles in the draft that show reference errors and making sure that the id actually got replaced.
Am I missing something here?
Thank you,
Ilya