I am trying to create a UIPath project that automates some job creation stuff in Microsoft Dynamics Great Plains Web Client. All that I need to automate is a fairly simple form entry, but I am not able to find reliable selectors so far. The web client app seems to be a single page Angular application that does not use IDs or specific data-attributes so I am not able to find reliable selectors. Angular seems to be storing any specific input info in javascript objects attached to each input. Every input selector seems to be defaulting to something like: webctrl parentid=âa000000000000000056800083584c00030100000000f1550000000000â tag=âINPUTâ . These types of selectors have been causing many unreliable behaviors especially when there are dynamic popup windows like showing in the screenshot example. Even though the UI Explorer is able to pinpoint the input, it selects the wrong input sometimes while running the project.
First Question:
It is my understanding that this selector is using the âparentIdâ (which I am guessing is generated by UIPath looking at the DOM tree to count the nested DIVs and create this ID) and the fact the element is an INPUT. Is that where this âparentIdâ attribute is coming from and if so wouldnât that be affected by dynamic HTML from popup windows in a single page app?
Second Question:
In cases like this one, what is the best practice? If I cannot find reliable selectors that will work through updates and other changes is it best to find another solution other than UI automation? Are reliable selectors not the foundation of a good reliable project that will be scalable moving forward?