Comments
We have long offered our customers “sample permissions” for the OnPrem solution based on the company's organizational roles. For example, there are basic roles that only contain rudimentary rights for logging in and creating (e.g. Sales Basic for creating sales documents, Purchase Basic for purchase orders, etc.). All booking functions for the respective business area are further (additional) roles, so you remain flexible, because often not everyone in a department is allowed to book. By creating smaller modules for specific tasks in addition to the basic roles, a rights concept can be set up flexibly. By using a descriptive name, a permission administrator can later recognize which permissions have been assigned to a user. With the new logic of referencing other permission sets, you also remain updateable when new versions are imported. Finally, customers can better identify themselves with their “own” roles and continue to manage permissions independently.
We've already build this very generic for every table and every cue is highly customizable - maybe something we can discuss about? Also available for free with limited number of cues:https://appsource.microsoft.com/de-DE/product/dynamics-365-business-central/PUBID.beyonditgmbhkiel%7CAID.beyond-cues%7CPAPPID.98fcfe84-9b76-4f8e-81a3-77d85907bdd2?tab=Overview
100% agree.I am currently setting up new GL Budget process for my current company. While investigating best practice and method, I have had to re-insert especially the date filter a hundred times. It seems bonkers this is not already included. Especially because we have a crooked fiscal year going 0107 - 3006.Whether it's a saved filter or report setting as Don Dyck suggests doesn't change much to. You would need to be able to extend/reduce the date if needed either way. I have no preference there. Though a report setting might make it more visible to the user.
