Protected data needs to be used. There are many types of entities which might attempt to use the data. Problem: If no standard way of accessing data exists, then each entity might attempt to build its own system for handing the sensitive data.
Recently I discovered (quite by accident) this neat little feature in Dynamics NAV (not sure which version this became available in to be honest).
The basic overview is this. If you have a function that takes a single parameter, you can assign the value to the function as if it is a property, rather than using the normal function call syntax. Here is a rather silly example scenario*:
In our blog post How to: Validate that Microsoft Dynamics NAV 2013 R2 is correctly configured to support Single Sign-on with Office 365, we presented the Microsoft Dynamics NAV Best Practices Analyzer, a tool that you can use in order to validate your single sign-on (SSO) configuration of Microsoft Dynamics NAV.
In Microsoft Dynamics NAV 2013 R2, we introduce the ability to set up single sign-on (SSO) between an Office 365 account and a Microsoft Dynamics NAV 2013 R2 account. More precisely, the Office 365 user account is linked to a Microsoft Dynamics NAV 2013 R2 user account.
If you are a manufacturing company using the Dynamics NAV Standard Cost Method, it is important that you understand the concept of Single Level and Rolled Up cost Shares.
When you Roll Up Standard Costs in Dynamics NAV, the system not only populates the Standard Cost Field for the manufactured items, but also populates the following fields: