We have a source system, Workday, where a specific attribute (e.g., xyz) is coming through as empty in the Workday end system, yet it is still displaying in ISC. How to resolve this?
is this connected through APIs or Saas?
it is workday saas connector
Do you mean as part of aggregation? If yes then can you check if you have any transform applied on the attribute in identity profile.
check once it may be custom attribute and have exact that filed info
Hello,
I have also observed this issue in WORKDAY source through we did not use the Saas connector but a Normal One indeed. Below are the steps which we used to troubleshoot and resolve the issue.
Pre-Requisites.
- Validate whether a new attribute that you are adding to WORKDAY source is part of WORKDAY setup or not.
- If its a Part of WORKDAY setup, then, what is the exact name of the attribute? Also check whether its a CUSTOM attribute because the way we will configure that attribute for aggregation from WORKDAY into ISC will change accordingly.
- Get the XML SOAP response from the WORKDAY team.
- Check whether the attribute values are populated in WORKDAY or not.
Development Steps.
If its a CUSTOM attribute, then,
- Go to Source
- Go to Account Schema.
- If the name of the custom attribute configured in WORKDAY as “Terminated_Comments”, then, the way you have to setup this attribute in account schema is “Terminated_Comments__c”
- Save the configurations
- Perform the single account aggregation for one of the identities for whom this attribute value is populated.
- Refresh the accounts page of that account/identity and check whether value is aggregated back successfully or not.
If its a OOTB attribute, then,
- Check whether attribute value is correct in account schema and its matching as per WORKDAY configuration. Its a Case Sensitive Configurations
- Also, check whether XPATH Mapping is correct or not as per expectations. You can use SOAP UI for checking the same.