Way back in Tip 226, we talked about the sitemap privilege tag that can be used to hide sitemap subarea links for users that don’t have a specific entity permission. One thing that you should know is that the privilege tag is not honored by Dynamics CRM mobile apps.
The rule of thumb is that if a user has permission to read an entity, the entity is enabled for mobile, and a link to that entity is displayed in the sitemap, the user will see that entity listed in the menu of CRM mobile apps.
As a practical consequence, if your users use CRM mobile apps on their smartphones or tablets, you may want to avoid putting every back-end custom entity in the settings area of the sitemap. For entities that are used for purposes like lookup lists, you want the entity to be available on mobile, but you probably don’t want the link to appear in the menu of the mobile apps. My recommendation is to not display the entity in the settings menu. Users who need to add records to these entities or manage the records in them can do so by running an Advanced Find query.
We have just discovered this limitation on our own and then found your post.
Is this considered as a defect by Microsoft?
We use the privilege tag a lot in our sitemap and we need to for various reasons. The fact that this is not supported on mobile apps creates a major headache for us.
See tip 500 http://crmtipoftheday.com/2015/10/20/captain-redlaces-mobile-manifesto/.
It is not considered a bug, the mobile platform is not as mature as the web interface, but each release it gets closer. See the connect links in tip 500 and vote for them to help make this a priority for the CRM product team
Thanks – I hadn’t seen your list. Quite a few of those are also on my list of improvement points for the mobile client. This issue doesn’t seem to have a Connect link but I definitely vote for it.