and more in a single search tool across platforms. Read the announcement here. |
03/24/2023 08:03 AM
Hello,
We're trying to pass the account name (whether from the task table or account table, both works) and account's customproperty31 in a REST connector for Servicedesk. The customproperty isn't getting populated from any request, instead it comes from a db connector we have, so we can't use reqattr.
So far, I've used these variables: ${task.accountName}, ${task.accountkey.customproperty31} and ${account.accountID} . While ticket gets created with no errors, in the ticket, we don't see the value in these attributes, we only see ${task.accountName} with no change.
Does anyone have any input on what variables I can use here? Attaching the whole createticketjson here code if that helps.
Thank you!
03/24/2023 12:52 PM
Can you try with ${account.customproperty31} and ${account.accountName}
03/24/2023 06:13 PM
Ideally ${task.accountName} and ${account.customproperty31} should work.
But try this as well ${account.name} and ${account.customproperty31}
Also looking your call I see below can you please explain what is that your are trying to do here? Are you trying to concatenate? If so then
\"additional_comments\": \"Application name: ${task.accountName} || Revocations: ${task.accountkey.customproperty31}\"
try below
\"additional_comments\": \"Application name: \" + ${task.accountName} + \" || \" + \"Revocations: \" ${account.customproperty31}\"
03/26/2023 09:05 PM
You may want to try the following:
${task?.accountKey?.customproperty31}
03/28/2023 03:15 AM
Hey Amit,
This one gives an error on task level and doesn't let the ticket be created.
03/28/2023 06:44 AM
04/03/2023 03:21 AM
Hey Saathvik,
I tried the suggestions, however all gave error. finally got it to work with ${task?.accountKey.customproperty31}.
And even that variable fails when there are special characters like ",{,},:, but it works with simple texts.
Thanks
03/28/2023 08:56 PM
Could you share your JSON?