Check out the connector Guide -
I have tried to add below code in debug for application but not working as: <entry key="sf_department” value=“fo_FODepartment?$format=json&$select=externalCode,department code”/>
I think this is an invalid XML formatting so please recheck once.
Hi Satheesh, Could you please help me to write this XML snippet or example.
Here’s a working example - but verify the actual field names in your SuccessFactors instance first,
<entry key=”sf_department” value=”fo_FODepartment?$formate=json& ; $select=externalCode,name”/>
@sagr0812 thanks for this. But i tried this not working . Do we need to add this sf_department atttribute in schema also or any other changes requried on application.
Yes, Sunil, You need to add sf_department to both the application schema and the attribute mapping and then run the aggregation to test it.
In the attribute mapping what should be the value for Navigation Path.
My suggestion is left blank for Navigation Path. Just make sure the Application Attribute is ‘sf_department’ and map it to your desired IIQ Identity Attribute.
Thanks for quick response. But we can not keep Navigation Path blank.
ok Sunil, in that case, you can set the Navigation Path to fo_FODepartment — that’s the OData entity you’re calling. So your mapping points to:
Navigation Path: fo_FODepartment
Application Attribute: sf_department
Identity Attribute: your IIQ attribute (e.g. department) try and see.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.