Web Services update account with all attributes

I essentially have the same question as this few years old post found here - Web Services update account with all attributes that never received any replies. All I see in the documentation is using plan.attribute name for the references.

I want to use a webservice connector during an update to retrieve all attributes. But only the one’s with changes have a value in the plan attributes. Is there some other tag I can use in my web body to to the identity/application and retrieve the values - $identity.value or $attributes.value?

Sample:

{
“action”:“updateUser”,
“users”:[
{
“VName”:“$plan.username$”,
“VPassword”: “XXXXXXXXXX”,
“VFullName”:“$plan.fullName$”,
“VEmail”:“$plan.email$”,
“VReportsTo”: “$plan.manager$”,
“VVaidityFrom”: “$plan.validityFrom$”,
“VValidityTo”: “$plan.validityTo$”,
“VDefaultCurrency”: “$plan.currency$”,
“VUIProfile”:“$plan.uiProfile$”,
“VRoles” :$plan.roles$,
“VGroups” :$plan.groups$
}
]
}

Then the logs show no values for those attributes, since only 1 was updated….

2025-08-04T11:55:54,757 DEBUG Workflow Event Thread 1 connector.webservices.v2.WebServiceFacadeV2:1657 - Operation: Update Account, dataMap: {planNativeIdentity=XXXXXXX1015891, VReportsTo=managerID, nativeIdentity=username}, endpoints count: 6

2025-08-04T11:55:54,757 DEBUG Workflow Event Thread 1 connector.webservices.v2.AbstractHttpRequestBuilder:133 - URL after replacing place holders :*****/vendavo/rest/lookup

2025-08-04T11:55:54,757 DEBUG Workflow Event Thread 1 connector.webservices.v2.AbstractHttpRequestBuilder:339 - Value for placeholder ‘‘plan.roles’’ is empty. Skipping…

2025-08-04T11:55:54,757 DEBUG Workflow Event Thread 1 connector.webservices.v2.AbstractHttpRequestBuilder:339 - Value for placeholder ‘‘plan.currency’’ is empty. Skipping…

2025-08-04T11:55:54,757 DEBUG Workflow Event Thread 1 connector.webservices.v2.AbstractHttpRequestBuilder:339 - Value for placeholder ‘‘plan.fullName’’ is empty. Skipping…

2025-08-04T11:55:54,757 DEBUG Workflow Event Thread 1 connector.webservices.v2.AbstractHttpRequestBuilder:339 - Value for placeholder ‘‘plan.email’’ is empty. Skipping…

Hi @ericlawson ,

If an attribute is not present in the attributeRequest section of the provisioning plan, it cannot be accessed using the $plan.attribute$ syntax.

you can use a Before Provisioning Rule to insert unchanged attributes into the attributeRequest. Once added, these attributes can then be referenced in your Web Services body using $plan.attribute$.

You can use following keywords in the Body along with the placeholder $
plan, response, application,getobject,authenticate

1 Like

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.