Unanswered

Condition Check Integer works with English Form but not Chinese Form

(0) Share

Report

Posted on by Community Power Pla...

I have created 2 forms, one in English and the other in Mandarin. However, the Flow for the Chinese form keeps failing at the Condition Check for Integer greater than. The error message is as follows:

Unable to process template language expressions for action 'Condition_Check_if_Value_more_than_RMB300_per_person' at line '1' and column '48534': 'The template language function 'greater' expects two parameter of matching types. The function was invoked with values of type 'String' and 'Integer' that do not match.'.

In the Chinese form, I have already applied a Restriction to ensure users can only enter a number. This is the same settings I made in the English form.

The screenshots below show the Flow condition used.

I suspect this may be a Form issue where the Chinese template is saving the restricted number field as a String and passing it to Automate, thus causing the error which does not occur in the English template.

Please help to test it out and help confirm if this is indeed the case?

Thank you.

Categories:

Building flows

I have the same question (0)

All responses (2)

Answers (1)

Paulie78 8,422 Moderator on at

Like (0)

Report

Try converting the form field response to a number (even though it is already one). You can do this in your condition or a compose action before your condition (then use the output of the compose as the left side of the condition).

In the expression editor use something like:
int(outputs('Get_response_details')?['body/whatIsTheValue'])

You need to replace the outputs('Get_response_details')?['body/whatIsTheValue'] with the dynamic content from your own form submission.

Was this reply helpful? Yes No
Verified answer

v-siky-msft on at

Like (0)

Report

Hi @Anonymous ,

It seems to be a bug that the answer should be Number type, but outputs as string (wrapped around double quotes) in the body of Get response details action.

As an alternative workaround, please wrap single quote around 300 to convert it to string type to eliminate compatible issue

Hope this helps.

Sik

Was this reply helpful? Yes No