Microsoft Dynamics GP 2016 was released in May, and for the last few months we have been going over the dozens of new features it delivers, first as introductions, and now in more detail. In our last blog entry for Microsoft Dynamics GP, we started taking a closer look at another new feature that we have previously introduced, the new OData service that you can deploy to democratize your Microsoft Dynamics GP data. The OData service enables you to manage access to your Microsoft Dynamics GP data for GP users so that they can build rich interactive reports in Power BI and Excel.
In our last entry, we covered how you deploy the OData service. Once you’ve finished installing it, you’ll need to ensure that your security in Microsoft Dynamics GP is set up properly. When your users connect to OData, they will do so using their Windows credentials, so you need to ensure that their GP user accounts are associated with their Windows credentials. You can do this in the User Setup screen, under the Directory Account tab. Then you want to set each user up with the proper role-based security access in the User Security Setup screen.
In the Security Task Setup screen, Microsoft has added a new type called “SQL Objects.” It includes “Stored Procedures” and “Views.” This enables you to grant access to these items if you decide to build custom security tasks and roles for OData reporting purposes.
