Need to pull data using SuccessFactors spoke (oData API) to Servicenow Staging tables

[Gaurav Gupta3]

Hi Everyone!!

Using SuccessFactors Spoke (oData API), tried to pull data from Successfactors to Servicenow staging tables. I was successful to pull data for three tables. However, all my efforts are failing for Locations table. Copied the OOB flow designer and want result only for 3 fields as of now, External ID, name and country.

Somehow after making some code as commented, I was able to pull the information for External id and Name, however country details are not populating at all.

[Mohith Devatte]

Hello @Gaurav Gupta3 ,

Please make sure you are checking "Retrieve all locations " while running the action and also don't give any date in ""retrieve modified locations from"  Input.

You are going in the right direction .I feel the success factor ODATA API which you are trying to HIT has no country data filled in for location database .

Can you just double check with your success factor team members that whether they have country data?

But I am pretty much sure that your resource path is correct  which used FOLOCATION API with JSON format.

We recently implemented ODATA and Compound API to pull data from success factors and we got the country data when we connected the snow instance to success factor test environment which had the correct data.

So i suggest you to check with SSF team whether they have correct data for country column in their location table.

Hope this helps 

Mark the answer correct if this helps you 

Thanks

[Gaurav Gupta3]

Hi Mohith
Thank you for the swift response which is really needed at this time.
Yes, I already check with SF admin, country details already exists for these external ids, however I will still reconfirm for the values used in the screenshot..  I doubt the code that is commented here especially "addressNavDEFLT"  contains country as a sub variable in oData API dictionary.   

Problem is, if I enable those code comments, then url is expanded with lot of information and it fails "

It generates the error on HTTP response log:
{
"error" : {
"code" : "COE_PROPERTY_NOT_FOUND", "message" : {
"lang" : "en-US", "value" : "[COE0021]Invalid property names: FOCorporateAddressDEFLT/stateNav. Please check the property name in Admin Center > OData API Data Dictionary or entity metadata. Ensure there were no data model changes that removed this field, and please execute a refresh metadata to ensure the cache is not corrupted."
}
}
}

[Mohith Devatte · Accepted solution]

@Gaurav Gupta3 This is not the issue from service now end .It is from success factor end .Because i just ran my OOB retrieve location action and in my payload i found the exact resource path like below.And also for few path i found country values as null and for few paths i got country codes correctly,

And this is the path i got in my flow execution record.Check if the same resource path you are getting in flow execution page.

FOLocation?$format=JSON&$expand=addressNavDEFLT/stateNav/picklistLabels

So in my ODATA dictionary model this path is there .But after seeing your error i think its clear that there is a data model change in SSF end .

Just check with SF admin whether they have this resource path or not.

Also see this article from SAP knowledge

centre

 https://userapps.support.sap.com/sap/support/knowledge/en/3248664

This above error is for different path PerPersonal/middleName. but the issue is same as yours and the article says the cause might be due to  field / property mentioned in the error being disabled.

See this below screenshot where i got FOCorporateAddressDEFLT path in my payload 

So i feel in SSF this field FOCorporateAddressDEFLT/stateNav is disabled as per the article .

contact your SF admin and get it checked by showing them the payload that you are getting and also the error .

Hope this helps 

Mark the answer correct if this helps you 

Thanks

[Gaurav Gupta3]

Hi Mohith

Solution is some of the fields were not activated from SuccessFactors end.  As soon the fields were activated, data started flowing in.  So all data is getting correctly loaded. 
Thank you for your help. 

Regards

Gaurav Gupta