Location value mapping

[Sajal Chatterje]

Hello comunity,

The location mapped to user profile is not the same as that of record present in service now for that location code.

Let me give you background----We have this okta integration in place with service now, but what is happening is.....in addition to other user related attributes , it is also mapping the location which is actually not present in service now location table(ideally location should be mapped from location table based on user location code) i.e locations are not in sync.

Can someone help me how should I start debugging the issue..if in Okta...where should I ask them to check in okta.?? Else in service now how may I implement script to check this type condition(location tagged to user profile is present in service now location table or not???

Kindly suggest me your thoughts.

Thanks,

Sajal

[Tony Chatfield1]

Hi, unfortunately your post contains no clear details of the integration, are you posting\putting records directly into your user table(s) or are you posting\putting to a temp table and transforming to target, or using a scripted rest api and end-point?

Assuming that the 'location' value passed from your integration is a unique map to one of your existing location field values?
If you are posting directly to the target table then you would need to look at a before insert\update BR to lookup the correct location record and map it to the location field.
If using a temp table\transform process you would normally use a before transform script to make the same sort of lookup and map the resulting value to your target.field
If using a scripted rest api, you would need to include the look-up\mapping in your script.