Applies to Product - Power Apps
What’s happening?
A bug was reported regarding the use of optional arguments in PowerFx when calling a Power Automate flow within the app editor. The syntax interpreter misinterpreted the curly braces used for optional arguments, leading to an "invalid argument" error when a text input was provided.
A bug was reported regarding the use of optional arguments in PowerFx when calling a Power Automate flow within the app editor. The syntax interpreter misinterpreted the curly braces used for optional arguments, leading to an "invalid argument" error when a text input was provided.
Reason:
This arose because the syntax interpreter inside the PowerFx function builder interpreted the curly braces for optional arguments as indicating a record type, rather than recognizing them as optional text input.
This arose because the syntax interpreter inside the PowerFx function builder interpreted the curly braces for optional arguments as indicating a record type, rather than recognizing them as optional text input.
Resolution:
To resolve this, the optional parameter in the Power Automate flow was changed to a required parameter. This adjustment prevented the parser from wrapping the argument in curly braces, allowing it to be recognized as the appropriate data type for the function call.
To resolve this, the optional parameter in the Power Automate flow was changed to a required parameter. This adjustment prevented the parser from wrapping the argument in curly braces, allowing it to be recognized as the appropriate data type for the function call.