Breaking news from around the world
Get the Bing + MSN extension
Now Available in Community - MBAS 2019 Presentation Videos
Catch the most popular sessions on demand and learn how Dynamics 365, Power BI, PowerApps, Microsoft Flow, and Excel are powering major transformations around the globe. | View Gallery
2019 release wave 2 Discover the latest updates to Dynamics 365Release overview guides and videos Release Plan | Early Access Availability
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Talent TechTalks | Upcoming TechTalks
A few days ago I’ve wrote about new possibilities in using of Limited Users in NAV 2016. I think this is big improvement, because we can use limited users for much more roles.
But I got a few comments about configuration limited users. OK, you can configure users as limited and this is all. Nothing more.
But people wants to configure what three additional application tables these limited users can use. Base on the standard NAV, this is not possible. These users get write access to a maximum of three application tables in the object range 0 – 99,999,999 other than the General Ledger Entry table. But system will count the first three used application tables beside the default tables. This is counted by the session. That means, users can use different three application tables in different sessions.
Some of administrators still want to limit these users on some specific tables. There is not feature for this requirement, but it can be made using User Permission Sets. We can create one permission set with all read permission on all tables (or less if you want this). Then, we can configure additional permission set with all permissions (insert, modify, delete) on our default 151 application tables. And on the end we can configure specific permission set based on our requirements for three additional tables.
Every time when we want to configure new limited user, we just need to add him these first two permission sets and one specific for him (or his role). In this case this limited user will have read permission to all tables and all other permissions to default tables and three we added to him. In this case, his three application tables will not depends of his first usage in session.
This is not some specific feature, but it is useful work around solution for configuration.
Business Applications communities