Dynamic Selector : Appear Message "variable is not defined in the current scope" even if it's defined

[Yoichi]

Hi Team,

When we set dynamic selector in selector editor, “variable is not defined in the current scope” appears even if it’s defined. This occurs when default value of the variable is empty.
I think it’s bug and hope it will be fixed.

Environment : Studio 22.4.4 + UiAutomation 22.4.7

If default value is empty, the message is shown.

If default value is set something, no problem.

Sample20220908-2.zip (7.9 KB)

Variable not defined in current scope

I am using a variable inside of a For Each Excel Row activity in the aaname field of the strict selector (aaname = ‘myvariable’). The purpose of this is to allow for accurate and dynamic targets/anchors when searching IDs that return multiple results, of which the ID searched for is one. Uipath is saying the variable is “not defined in the current scope” even though I defined in the For Each Excel Row activity and the click activity using the variable is inside the same Excel activity. Any ideas…

動的セレクターがうまくいかないです

こんにちは 既存のトピックを拝見しましたが、解決せず、同内容を質問させていただきます [20220908_動的セレクタ不能] 右クリックで変数指定をしているにもかかわらず、 スコープ内で定義されていませんと表示されてしまい、変数認識できません ↑のトピックでは パッケージのバージョン違いという解決方法でしたが、 当方の環境のバージョンは以下の通りです UiPath.System.Activities: [22.4.4] UiPath.UIAutomation.Activities: [22.4.4] 先日までは起こらなかった事象なのですが、 実装＆テストを進めていたら起こるようになりました なにきっかけで起こるようになったのか不明です… どなたかお知恵を貸していただきたくお願いします

Regards,

[AdityaVN (Aditya Vaddiraju)]

Hi @Yoichi

can you check if the same variable name is present in a different scope or with different lower/upper case

[Yoichi]

Hi,

This is bug report. Can you check the above attached sample (Sample20220908-2.zip)? Probably you can reproduce this matter.

Regards,

[loginerror (Maciej Kuźmicz)]

Hi @Yoichi

Could you please explain your use case?

On the first look, it is working as expected. The design time needs something to use when validating the selectors, and it uses the default value of the used variable.

Thus, having the default of the variable be empty throws an according message.

Is your use case requiring you to validate a selector with nothing for your value?

[Yoichi]

Hi @loginerror ,

Thank you for your reply.

@loginerror

Thus, having the default of the variable be empty throws an according message.

I don’t think it’s proper message in this situation.
Most users think this means not default value isn’t set but variable isn’t defined, as the above linked topic.
In addition, this message is same as case that variable isn’t defined as the following.

Default value of the variable is empty.

The variable is not defined.

So, I hope the message will be reviewed. (For example, “Default value is not set” etc.)

Regards,

[Josh_James]

Hello - Has anyone found a solution to this issue? I am also facing this exact same problem.

[Tony_Andy]

I’ve just faced the same issue. Turns out as soon as I give it the default value, the message disappeared. Looks like the one of the guys above ( sorry for not knowing how to mention) said correctly. The error message should relate to the default value not the scope.