Microsoft Dynamics 365 | Integration, Dataverse...

How to hide views based on Sitemap selection?

(0) Share

Report

Posted on by Community Member

Hello D365 Community,

Tried searching through the forums first and found this question really hasn't been answered yet: Thread 1, Thread 2, Thread 3.

In our association we will have multiple types of records exist under both the Account and Contact entities. For example, Contact might house both members and nonmembers; Account might house clubs, districts, and other administrative units. When it comes to designing the UI/UX, we want our users to be able to click "Members" on the Sitemap—which would direct to the Contact entity—and only be able to select system and custom views related to members. I'm not seeing a way to hide views to accomplish this to where if a user clicks "Members" they do not have to sift through all the views for Contact we might have. How can we go about solving this?

To clarify:

We do not want to deactivate these other views. They will still be used—just on other screens/grids.
We do not want to create separate entities for each of these record types. (I.e. we do not want to create a Member entity, Nonmember entity, and so on just to accomplish this.)

Any thoughts on how to solve this? Appreciate any thoughts and help.

I have the same question (0)

All responses (4)

Answers (0)

Suggested answer

Miguel Lourenco on at

Like (0)

Report

Hi

I believe you cannot hide views but you can choose what view it will open by default at least. I went to the sitemap and changed it to:

Being the url:

/main.aspx?pagetype=entitylist&etn=account&viewid={61273827-328E-E011-95AE-00155D9CFA03}

Of course you need to change to contact and replace the guid with yours view's id.

With this whenever your users clicks on "nonmembers" the contacts will open with the view you set in the URL. The same for members.

hope it helps!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks Miguel. That doesn't get us quite where we want, but that does help some.

Is there a way to utilize web resources to accomplish this, maybe? Whether adding a web resource to views (not sure that's possible), or calling web resource straight from the Sitemap that controls the visibility of these views? Any thoughts on that?

Was this reply helpful? Yes No
Suggested answer

ba365guy 2,950 on at

Like (1)

Report

Create two separate apps.

1. App with Member specific Components (Views, Forms, Sub-grids, etc.)

2. App with Non-member specific Components

Just give it a thought!

Was this reply helpful? Yes No
GreenPowerBI 10 on at

Like (0)

Report

Hi - i am in the same situation, did you ever find a proper solution for this? thanks.

Was this reply helpful? Yes No