Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
We have started to roll out Forecasting in our organization for selected users.
We would like to only show Forecasting in the sitemap for users who will be using it. However, unlike normal tables/entities, the visibility of the Forecasting doesn't seem to be controlled by security privileges. E.g., if you don't have read privilege for the Lead table, it will not show in the sitemap (and this is great).
Right now, all users can see Forecasting in the sitemap even though no one has any forecasting security role assigned.
I can see that the difference compared to a 'normal' table is, that Forecasting in the sitemap is linking to a control and not a view: like this:
Iis there any way to get around this so we can hide it for users who don't need it but still use the same app?
Business Applications communities