Forcing a non-default View in MDA?

(0) Share

Report

Posted on by CU13112050-0

Hello,

I have a Contacts table. Some of these contacts have a field value of Type = Client.

In my MDA navigation, I would like to be able to go to an "All Contacts" View (list/table). This is easy and works as intended. The Default View for the Contacts table View is the system generated All Active Contacts view. No problem.

In my MDA navigation, I would also like to be able to go to an "All Clients" View (list/table). This is where I am having a problem. The Default View for the Contacts table View remains "All Active Contacts" view. I created a separate "Active Clients" view. But I cannot set this to Default, because then that affects the "All Active Contacts" view as default.

How do I force MDA to let me open one view from the Contacts menu item on the left (the Active Contacts view (default)), and another/different view from the Clients menu item on the left (the Active Clients view (not default))?

Attached are screen shots for visual aid.

Thank you very much for your time and help!

Categories:

Microsoft Dataverse with Power Apps

I have the same question (0)

All responses (3)

Answers (1)

JonDoesFlow 1,304 on at

Like (0)

Report
Copy link

Link copied!

Go to the MDA designer, and click on the Contact part of your MDA, select the views, and then on the right hand side, click the three dots on each of the views you want to remove, and click remove.
Don't forget to publish afterwards

---------------------------------------------------------------------------

If I have helped you with an answer, please accept this post as a solution and thumbs up my reply. Thanks !

Blog - JonDoesFlow
Twitter - JonDoesFlow
YouTube - JonDoesFlow

Was this reply helpful? Yes No
Verified answer

SteRe 254 on at

Like (0)

Report
Copy link

Link copied!
The suggested way won't work. Even if you add the entity twice to your app and change the settings of available view to one entry only it will affect the whole entity. So your other contact views will be gone then too.
In the past we did exactly the same by adding another entry to site map of type URL and having relative URL to the specific view. Unfortunately I don't have access to this environment any longer to check the specific syntax to use.

Edit: I think I found it again: Just add a new entry type URL to sitemap and use following target:
/main.aspx?pagetype=entitylist&etn=contact&viewid=<guide of your view>&viewType=1039
last parameter (viewType) could be skipped probably as it is added automatically. Just try both options.

Was this reply helpful? Yes No
CU13112050-0 39 on at

Like (0)

Report
Copy link

Link copied!

Thank you I will try to check this today and report back!

Was this reply helpful? Yes No