Hi Team,
We are using EPIC SER OOTB connector and trying to push our own generated Provider ID at item no: .1
But it seems like sailpoint only generating records using nxt available provider id instead of our generated value. Somehow it feels like it’s connector limitation or Im missing something else.
Anyone faced same situation? Any insights are helpful, thanks!
@gourab Can you post your SER attribute mapping configuration for review? How are you generating the value for .1 and have you confirmed the attribute is mapped correctly in the app config?
If so, try having the Interconnect admins do some trace logging of the transactions to confirm that .1 is being sent in the import.
There is a hidden keyword that will enable it, ask your SailPoint rep if they will tell it to you. It is pretty trivial to figure out if you think about how this all works. We discussed this in the Epic Group, but with the Community rebuild that has disappeared for the time being, but I am told it should be coming back, eventually.
I opened a ticket to SP and got the answer:
We checked this further, and you need to enable a setting within your connector: createWithEpicId.
Note -
Before enabling this configuration, you must check with the Epic product team to ensure you qualify to use the feature. The optional source config item “createWithEpicId” when set to “true” will cause the “providerId” create policy field to specify the Epic ID
PATCH - /v3/sources/:id
[{"op": "add","path": "/connectorAttributes/createWithEpicId","value": true}]