Answered

How to disable hyperlinks on views and subgrids

(0) Share

Report

Posted on by tschopp

311

In a model-driven app, is there a way to disable hyperlinks on views and subgrids that take the user to the lookup table record instead of the primary table record?

Categories:

Building Power Apps

I have the same question (0)

All responses (6)

Answers (1)

GarethPrisk 2,828 on at

Like (1)

Report
There's no quick or supported way to do this. It is possible, but I would instead leverage this existing functionality instead of fighting against it. This is typically a desired "click through" behavior that can be a major benefit of MDA views.

I can appreciate that users find it irritating until they are used to how this works. It is especially challenging for intersect entities (where the lookups are essential to show how things are related).

A few tips:

DO NOT put a Lookup as the first column in a view, if you can help it

Instead use the Primary field (prefix_name)

Set the name to something automatically, if the records aren't named by users

DO set correct expectations for users in training

Explain why hyperlinks exist and what lookups to other entities are

Instruct them to click into the row's white space to open a record

DO consider your MDA theme

You can make the lookup field links more obvious

Was this reply helpful? Yes No
tschopp 311 on at

Like (0)

Report

@GarethPrisk
Thanks for the tips. I understand where this functionality can be useful once users are accustomed to it. But there are some cases where our users would never need to click through to the lookup table record. Since you said "it is possible", I'm curious how that might be done. Is there a way to access and disable those links using JavaScript or JQuery?

Was this reply helpful? Yes No
Verified answer

StalinPonnusamy Super User 2024 Season 1 on at

Like (1)

Report

As Gareth mentioned, accessing DOM objects is not supported but here is the article to disable the lookup hyperlink.

https://vishalgrade.com/2018/02/12/how-to-disable-hyperlink-property-of-a-lookup-in-dynamics-crm/
The same concept we can apply for views.

Another option is to have a text field to store the lookup name. So that you can display it on the views. The drawback is this text field needs to be updated whenever lookup changes.

Was this reply helpful? Yes No
GarethPrisk 2,828 on at

Like (1)

Report

@tschopp as @StalinPonnusamy posted, this would be done by unsupported code using the DOM. I can't recommend this, whatsoever. If only because it sets poor expectations for users, and there is no guarantee it will work in all scenarios or long-term.

Since they won't ever need to click through, could you simply set the Primary Field, or a custom text field, to be a friendly display name for the record?

For example, if it was an Account Contact table, and you had a lookup to Account and Contact, could you set Primary Field via sync workflow to be "{Account Name} | {Contact Name}" or equivalent?

Then you simply show just the Primary field, or custom text field, in your views and the users won't be able to click-through.

In other places, they may need to/want to click-through and they'll then be able to and know how/when.

Was this reply helpful? Yes No
tschopp 311 on at

Like (0)

Report

@GarethPrisk - I've used that idea on another table and it works well. But for the table I'm working on now, the primary name field is an auto number with values that are meaningless to the users. So I could add it to the subgrid, but not optimal.

@StalinPonnusamy - Thanks for the link. I agree that that does not look like a good idea and will hold off on doing that until the users buy off on the risks. Your idea of adding a separate text field is interesting though. We'll keep that under consideration.

Was this reply helpful? Yes No
GarethPrisk 2,828 on at

Like (1)

Report

@tschopp I'd add another text field that is meaningful to the users and display that.

Always good to drive positive UX, where the user's get the best contextual info, and has the least cognitive load.

Was this reply helpful? Yes No