Hi,
In Call a webhook, is it not possible to use a slice with the USEREMAIL() function applied or the USEREMAIL() function itself?
Thank you.
You may want to elaborate about the web hook.
For example, the following web hook works. The web hook runs on the slice 'My Orders"
The “My Orders” slice is in turn based on the following row filter expression, which is USEREMAIL() based. So the web hook updates records only related to the Orders that belong to the logged in user based on USEREMAIL()
1 Like
Thank you for your reply. I would appreciate it if you could review the contents of mine below.
- There is the slice that has another slice in an expression.
The result of the slice expression Test:
- And the webhook is like this:
The Body expression is like this:
{
“Action”: “Edit”,
“Properties”: {
“Locale”: “ko-KR”,
“Timezone”: “Korea Standard Time”
},
“Rows”: [
<<START: filter(“D_연결대상기업_G3_SRO_CurrentMyOwnCompany”,and(
1=1,
1=1
))>>
<<START: FILTER(“D_시산표_G6_TUAD”,and(
1=1,
1=1,
1=1))>>
{
“D_PERIOD_G2_TUAD”: “<<[D_PERIOD_G2_TUAD]>>”,
“D_SEPARATE_G3_TUAD”: “<<[D_SEPARATE_G3_TUAD]>>”,
“D_시산표Account”: “<<[D_시산표Account]>>”,
“D_시산표손익마감”: 100000
}
<>
<>
]
}
And,
Audit Log Details
Action Details
REST API:
{
“Action”: “Edit”,
“Properties”: {},
“Rows”:
}
Properties:
{
“RestAPIVersion”: 2,
“TableName”: “D_시산표_G6_TUAD”,
“AppTemplateVersion”: “1.000668”,
“Action”: “Edit”,
“Errors”: “No rows are present.”,
“AppTemplateName”: “24a60fe5-ff1b-475c-ad9f-…”,
“Operation”: “REST API invoke”,
“RecordType”: “Start”,
“Result”: “Failure”
}
- I think the difference yours and mine is that my table has a compound key and my slice expression use another slice(D_USER_G3_SRO_Current), and my webhook Body expression does not have ‘RunAsUserEmail’.
Thank you.
My suggestion will be to try to simplify the complex structure of your Webbook body expressions. Are the slices on the same table? The web hook seems to require a table to send request to.
If possible you may want to filter the records that you would like to be sent to the web hook in the slices itself rather than having nested slice <> expressions that could make the error detection more difficult.
1 Like