Hi Beth,
Do you actually mean to have the
not in there? You said you're checking if the Request Date IS null, so that's your equals function. If you mean that you're checking if the Request is NOT null, then the parentheses that belongs to the
not function should go right after the
null).
Power Automate is complaining because currently the "end paren" of the
not function is all the way at the end, and it's seeing the
,1 as a parameter for the
not.
Does that make sense?
Sandy
PS - Hello from nearby Naples :-) [I moved there last Feb, but I can't see how to get the UG to change my location :-) ]
------------------------------
Sandy Ussia
Business Applications MVP
Technical Evangelist, Lightning Tools
Co-Founder, NLightning
sandy@sandyu.comUnited States (currently)
------------------------------
Original Message:
Sent: Jan 15, 2023 09:49 AM
From: Beth Beck
Subject: Do Until Multiple Expression Error
I am using a Do Until with two conditions and I keep getting this error:
Unable to process template language expressions for action 'Do_until' at line '1' and column '40434': 'The template language function 'not' expects one parameter: the boolean value to negate. The function was invoked with '2' parameters. Please see https://aka.ms/logicex
My expression is: If the Request Date is empty/null AND the 'varNotOverLoop' is 1. I don't get any errors when I save Flow. I've gone back into it multiple times to ensure the expression hasn't changed.
@and(not(equals(outputs('Update_NotOver_PAS_Rejected')?['body/RequestDate'], null),equals(variables('varNotOverLoop'), 1)))
I've tried everything detailed in this blog (and another blog that has similar recommendations) Fix the InvalidTemplate error in Power Automate | Encodian Could it be it doesn't work well with a 'null' value? Any thoughts as to what is wrong?
Note: I use a single expression in another flow with Do Until and it works fine.
------------------------------
Beth Beck
O365 Business Analyst
Fort Myers FL
------------------------------