Leveraging Intelligent Recommendations for Operational Transformation. AMS Partners click HERE | EMEA/APJ Partners click HERE |
07/17/2024 12:39 AM
Hi All,
I have passed the users seondary email in the request body for a POST API call. I can see in the logs that ${user.secondaryemail} is not getting resolved. Everything else is getting resolved.
Request JSON:
"{\"FirstName\": \"${user.firstname}\",\"LastName\": \"${user.lastname}\",\"BusinessUnit\": \"United States BU\",\"LegalEntity\":\"XXXXX Corporation\", \"PersonType\": \"EMP\", \"ResourceEmail\": \"${user.secondaryemail}\", \"ResourceEndDate\": \"4712-12-31\", \"ResourceParentOrganizationName\": \"XXXX\", \"ResourceOrganizationName\": \"XXXX\", \"ResourceOrgRoleCode\": \"SERVICE_ADMINISTRATOR\"}"
In Logs:
Calling Webservice Url - https://api.xxxx.com/rs/v1/fusion/users/resourceUsers with httpParams - [FirstName:Andrew, LastName:Kane, BusinessUnit:United States BU, LegalEntity:XXXX Corporation, PersonType:EMP, ResourceEmail:${user.secondaryemail}, ResourceEndDate:4712-12-31, ResourceParentOrganizationName:XXXX Organization, ResourceOrganizationName:XXXX Organization, ResourceOrgRoleCode:SERVICE_ADMINISTRATOR]
As we can see that everything except user.secondaryemail is getting resolved. An I doing something wrong?.
Should it be ${user.secondaryEmail} and not ${user.secondaryemail} i.e 'E' should be in capital in Email?.
Please advice.
Thanks.
Solved! Go to Solution.
07/17/2024 01:28 AM - edited 07/17/2024 02:12 AM
Hello @AS5278 ,
Please use
"${user.secondaryEmail}",
Thanks.
07/17/2024 01:42 AM
Hi @AS5278
Check out the REST developer's handbook for binding variables
07/17/2024 02:00 AM