ArcherPoint Dynamics NAV Developer Digest - vol 139
The NAV community, including the ArcherPoint technical staff, is made up of developers, project managers, and consultants who are constantly communicating, with the common goal of sharing helpful information with one another to help customers be more successful.
As they run into issues and questions, find the answers, and make new discoveries, they post them on blogs, forums, social media...so everyone can benefit. We in Marketing watch these interactions and never cease to be amazed by the creativity, dedication, and brainpower we’re so fortunate to have in this community—so we thought, wouldn’t it be great to share this great information with everyone who might not have the time to check out the multitude of resources out there? So, the ArcherPoint Microsoft Dynamics NAV Developer Digest was born. Each week, we present a collection of thoughts and findings from NAV experts and devotees around the world. We hope these insights will benefit you, too.
Watch Out, “Access by Permissions” in Dynamics NAV Can Really Bite
Consider the following:
You assign ES_ITEM_CREATE to Michael and John. Michael creates and maintains the item cards. John is Michael’s backup and he too creates and maintains the item cards. In addition to being Michael’s backup, John uses the Requisition Worksheets to create Purchase Orders.
After assigning permissions, Michael reports that he can’t see all of the fields on the item card. Michael and John compare screens and notice that many fields are missing from Michael’s screen. Including Manufacturing Policy, Reorder Point, Minimum Inventory, Maximum Inventory…you get the idea. This seems strange since they both have the same ES_ITEM_CREATE permission.
The culprit is the “Access by Permission.” You won’t get an error, you won’t get a warning. You just have to know where to look.
Where to look:
- From the DEV environment object designer, select the Item Card Page and choose Design.
- Locate the offending field and highlight the line.
- Look at the offending fields properties (Shift + F4)
- Scroll down until you see the “AccessByPermission” property.
- AH HA!
The Access by Permissions property lets you know that the user will require Read Access to the “Req. Worksheet Temp.” TableData in order to see this particular field.
John was able to see the fields because he had supplementary permissions that allowed the fields to be visible to him. Michael will need additional permissions to allow him to see the special fields with the “AccessByPermission” property activated.
Rampant cc’ing on emails leads workers and managers to squander precious time sorting through unnecessary messages. David De Cremer’s research shows it can have another cost: reduced trust. This is ironic as some people include others in an email thread in good faith. They believe the benefits of transparency and collaboration outweigh the costs of excess emails. What they may not realize is how all this surplus communication is eroding the very goals they seek to support through their excess collaboration.
Stay abreast of what is new in the Microsoft Dynamics NAV community and at ArcherPoint by subscribing to our monthly newsletter, Better Business, by completing the form in our Resource Center.
And, if you are interested in NAV development, be sure to see our collection of NAV Development Blogs.