Microsoft has addressed this friction point with a targeted UI-level enhancement for Dynamics 365 Field Service: the ability to disable clickthrough on lookup values in forms. Tracked on the Microsoft AI at Work roadmap under ID 576886 and released to General Availability in Worldwide (Standard Multi-Tenant) cloud instances in June 2026 (specifically June 19, 2026, according to Microsoft Learn's 2026 release wave 1 documentation), this feature allows makers and administrators to render displayed lookup values as plain text rather than active hyperlinks.
While it may not have the flashy marketing budget of an autonomous AI agent, this kind of granular form control is the bread and butter of practical enterprise IT administration. Here is a complete breakdown of how the control works, why the roadmap metadata can be slightly misleading at first glance, and how to configure it properly in Power Apps.
What Disabling Lookup Clickthrough Actually Does
By default, when alookup field is populated on a Dynamics 365 form, the displayed text acts as a direct navigation link to the underlying record. In a back-office desktop scenario, clicking through to inspect an associated account or contact is often helpful. For frontline workers using the Field Service mobile app—or even dispatchers moving rapidly through web forms—those hyperlinks are frequently just landmines that interrupt task flow.
When a maker enables the new clickthrough restriction on a lookup control, the visual and functional behavior changes in a specific, narrow way:
- Plain-Text Rendering: The lookup value is displayed as standard, non-interactive text instead of a hyperlink.
- Navigation Prevention: Selecting or tapping the populated value no longer opens the related record, keeping the technician anchored to their current form.
- UI-Level Scope: As noted in Microsoft's release plan documentation, this is strictly a UI-level control applied per form and per lookup field. It does not require enabling an environment-wide platform feature flag, and it does not alter Dataverse table relationships, security roles, or underlying record permissions. If a user has permission to view that related record elsewhere in the app, they still can; they just won't stumble into it by grazing a lookup box on the configured form.
Clearing Up the "Web" Platform Tag vs. Actual Scope
If you spotted Roadmap ID 576886 on the Microsoft 365 AI at Work Roadmap—which began absorbing Dynamics 365, Power Platform, and Dataverse capabilities as Microsoft archived standalone release plans in late 2026 —you might have noticed that the roadmap metadata lists Web as the sole platform tag.
In enterprise administration, trusting a single metadata tag without checking the technical documentation is a recipe for confusion. Both the roadmap description itself and Microsoft Learn's official Field Service guidance explicitly confirm that this setting applies across both web and mobile forms. Because form customizations are authored inside the web-based Power Apps maker portal, the roadmap categorizes the administrative surface under Web, even though frontline mobile users are the primary beneficiaries of the change.
Step-by-Step: How to Disable Clickthrough on a Lookup Field
Microsoft's high-level release notes summarize the setup as selecting the lookup field in Power Apps and toggling the disable option. However, Microsoft Learn's dedicated implementation guide for Dynamics 365 Field Service provides the exact component-level path makers need to follow inside the form designer, including a critical naming trap to avoid.
To disable lookup clickthrough on a standard form lookup:
- Open the Form Designer: Sign in to Power Apps and open the specific table form where you want to modify the lookup behavior. (You must have sufficient security permissions to edit and publish model-driven forms.)
- Select the Lookup Field: Locate and select the existing lookup field on the form canvas, or configure a new Power Apps lookup component.
- Open the Components Property: In the properties pane for that lookup field, navigate to the Components section and select + Component.
- Choose the Exact Control Name: Search for Lookup Control. Microsoft Learn specifically warns makers to select Lookup Control (two words, no hyphen) and not Look-up Control (hyphenated). Picking the wrong control is a classic Power Apps gotcha that will leave you wondering why the property is missing.
- Configure the Clickthrough Property: Locate the Lookup clickthrough property and set its value to Disable lookup clickthrough (also referred to in release notes as Disable click-through of lookup value).
- Apply and Publish: Select Done, then Save and publish the form.
What Success Looks Like (and the Mobile Sync Requirement)
On web forms, refreshing the browser after publishing will immediately render the targeted lookup value as plain text.
For technicians using the Dynamics 365 Field Service mobile app, the change will not appear instantaneously upon publishing. Microsoft notes that the mobile application reflects the updated form configuration after the device completes its next sync. If you are testing this change on a test tablet or phone, force or wait for a mobile sync before troubleshooting why the hyperlink is still active.
If you ever need to revert the behavior, simply return to the form in Power Apps, re-enable clickthrough on the component (or switch back to the default display mode), and republish the form.
Standard Lookup Control vs. Drawer Lookup Control
While configuring lookup behavior for mobile technicians, administrators may also encounter documentation for Microsoft's Drawer Lookup Control—a mobile-focused lookup experience that uses a modern bottom-sheet interface to speed up selecting values from lists.
It is important not to conflate the two controls, as they have different support boundaries documented on Microsoft Learn:
| Feature / Constraint | Standard Lookup Control (Clickthrough Disabled) | Drawer Lookup Control (Mobile Lookup) |
|---|---|---|
| Component Name in Power Apps | Lookup Control (not Look-up Control) | Drawer Lookup Control |
| Clickthrough Disabling Supported? | Yes, via the Disable lookup clickthrough property | Yes, configured within the Drawer Lookup Control setup |
| Supported Platforms | Web and Mobile | Mobile and Tablet only (may work on web, but unsupported on web) |
| Multi-Table Lookups | Standard lookup support | Not supported for multi-table (polymorphic) lookups |
If your goal is simply to stop technicians and web users from accidentally clicking hyperlinks on existing forms without introducing a mobile-only bottom-sheet control, stick to the standard Lookup Control instructions above. If you are already deploying the Drawer Lookup Control for phones and tablets, you can configure the Disable lookup clickthrough setting directly inside that drawer component's properties while enabling its mobile and tablet device experiences.
Practical Impact for IT Admins and Makers
Why does a minor form property deserve attention from Dynamics 365 administrators? Because user adoption in field service lives and dies by interface friction. Frontline technicians often work with gloved hands, in poor lighting, or on bouncing vehicle mounts. Every accidental navigation event forces the user to wait for a related form to load, realize they left their work order, hit the back button, and reorient themselves on the page.
Because this setting is configured per lookup and per form rather than globally across an environment, makers can apply surgical judgment. For instance, on a technician's primary Work Order form, you might leave clickthrough enabled on the Customer Asset lookup so the tech can inspect equipment history, while disabling clickthrough on administrative lookups like Service Territory, Price List, or Billing Account that a tech needs to see for context but never needs to open. That balance keeps critical reference data visible on screen while stripping away unnecessary navigation traps.