When using the web automation controls, the IP address of the UI Element is hard coded. So if we build a flow for the test environment, we can't migrate to production. We need the UI Elements to honor the browser variable like all the other web controls do.
This is a show stopper for us.
Solved! Go to Solution.
This name doesn't matter, it has nothing to do with which window or UI element you are trying to access. You need the variable only for the run browser session.
https://docs.microsoft.com/en-us/power-automate/desktop-flows/ui-elements#element-types
https://docs.microsoft.com/en-us/power-automate/desktop-flows/automation-web
You can always use variables in selectors through the selector builder, also to respect different environments: https://docs.microsoft.com/en-us/power-automate/desktop-flows/ui-elements#element-properties
I tried that but it doesn't make sense to me. I pulled up the list of UI Elements, edit the selector and brought up the builder. The selector name is "Web Page 'http://198.172.62.2:10100/web/database". Clicked custom and the value in the box is ":desktop > domcontainer". So how do I replace the IP:Port with a variable I already have defined?
Just click on the dot menu and rename. It is just a name, the selector is generic for browser.
I know I can change the name of the selector in the master list of UI elements; however, that name does not show as changed in the "Populate text Field on web page" UI Element selector. Also changing the label doesn't address the feature of how to set it to a variable. Can you point me to a video or web page tutorial?
This name doesn't matter, it has nothing to do with which window or UI element you are trying to access. You need the variable only for the run browser session.
https://docs.microsoft.com/en-us/power-automate/desktop-flows/ui-elements#element-types
https://docs.microsoft.com/en-us/power-automate/desktop-flows/automation-web
Oooohh, gotcha. So basically the IP address is basically an auto-generated label. They really should update the documentation on that part. Thanks for the excellent help and you patience.
Yes, I agree, it's quite confusing! Especially not ideal is the limitation you were referring to, not being able to fully rename it.