Use case: Element selectors for Microsoft Dynamics
When configuring the Adoption settings for Microsoft Dynamics Adopt guides, use the Element selectors on this page to:
Maximize the stability and reliability of element selection by avoiding dynamic identifiers.
Enhance guide resistance to webpage changes from Workday.
Element selectors for Microsoft Dynamics
From the Adoption settings tab > Settings subtab in Nexthink, for the Microsoft Dynamics web application configured in Nexthink:
Ignored element IDs:
form_.*
Element ID replacement: Instruct the system to remove dynamic components—in this case, numbers—from ID or class-name selectors, and only keep the static segments of interest.
In the ID field, enter
(.+)_\d+_(.+)
. This code represents any number within the element ID.In the Replacer field, enter
[id^="$1"][id$="$2"]
. This code represents the element ID segments before and after the number within the ID.See Element ID replacement example below.
Ignored element class names:
.*(\d+).*
This code represents numbers within class names.Included element custom attribute names:
aria-label, data-automation-id, data-uxi-widget-type, data-uxi-element-id, role, name, title, aria-describedby, data-dyn-controlname, data-dyn-content, data-dyn-form-name, data-dyn-placeholder, data-dyn-role, data-dyn-title, aria-expanded, dyn-data-optional-label, alt, data-dyn-columnname, data-dyn-form-name, data-dyn-title, data-dyn-mappedtab, command, data-handler, placeholder
Use Nexthink default configurations for the remaining Adoption settings, including Guide defaults.
Your configuration should look like the image below.

Last updated
Was this helpful?