cf_SecurityGroupName is also added in Workday but still getting the same error.
I have been looking into docs and in discussion forums to see if I can find any solution but not able to.
Anyone has come across to such issue before? Any input/help will be highly appreciated.
Hello Prachi,
I did try the troubleshooting approach and added the custom attribute, but it still throws same error.
Please let me know if I am missing anything or I need to perform any extra step.
Thanks!!
Hi @mpatel2024 ,
Just because the field is added in Workday doesn’t mean it’s automatically accessible via the API. Make sure that the field is exposed in the Workday report (RaaS) and accessible through the API. You can try accessing via postman and see the response!
Another might be to ensure that the field is correctly mapped to the Security Group object type in the Workday connector configuration.
Hello Prashanth,
Thanks for replying. The field is already been created in workday but the documentation did not say where it needs to be included. If you can provide more detail, It would be helpful. I appreciate your help.
Thank you!!
Exception during aggregation of Object Type SECURITY_GROUPS on Application Workday Accounts - SB [source]. Reason: java.lang.RuntimeException: An error occurred while aggregating Application Workday Accounts - SB [source] “error”:“invalid request: WQL error.”,“errors”:[{“error”:“Enter a valid report field. This field is invalid: cf_SecurityGroupName.”,“field”:“cf_SecurityGroupName”,“location”:“Invalid SELECT clause”}]
Ask your workday team to add cf_SecurityGroupName field in Workday and run the entitlement aggregation again. Please follow the screenshot below: “field to be added in workday”.
They did add that to the Workday even though we are still having the same error, are there any additional steps we need to do in the Workday after adding the field or in the IDN.