Answered

If condition is not working as expected

(0) Share

Report

Posted on by Zdahn

I'm doing a test in Google Translate to detect if the text input is in English with it's auto detect feature so I dont need to translate it.

"IF" condition is not working as expected - what could be wrong with my flow.

On my first attempt it was working fine, after I tried using new variables to populate in text field, something did not worked well after.

Really appreciate if you could help me on this.

Thanks

Categories:

Power Automate Desktop

All responses (4)

Answers (1)

Sort by

Verified answer

VJR 7,635 on at

Like
a
(0)

Report
Copy link

Link copied!

In the variables pane TestLangEnglish appears to be a table of rows and columns, so don't compare it like a string in the If statement. Use the Row Column notation. Variable data types - Power Automate | Microsoft Learn
Zdahn 73 on at

Like
a
(0)

Report
Copy link

Link copied!

Is that really possible to have a table variable for the extract data flow when the value of extracted is a text already?
In the Advance Setting for the Extract Data flow - I selected Single value and appeared just as I expected. But still did not worked.

Could you help me with this please.
Zdahn 73 on at

Like
a
(0)

Report
Copy link

Link copied!

I mean, I'm still not getting the text value "English - detected" when I run the flow, it's the table that appearing, and I don't know how I did it on my first run.

And now it's becoming more confusing that the Extracted value for my translated text worked to appear on my Display message flow as expected even the format is in table.
valor 4 on at

Like
a
(1)

Report
Copy link

Link copied!
Since I found this thread and was confused, let me explain.

When you use the "Extract data from web page" action, the output is a data table. If you're extracting, as in the question, a single web element then the datatable variable data type will have one column and one row. Here in the "display message" or even the variable output at the end of a flow run causes the "observer effect" and casts the data type to a string -- which makes you THINK you have the right value.

TLDR: When using "extract" access the extracted value with
%VariableName[0][0]%