on
RE:
Great idea, will save a lot of stress for the client and partner receiving the call from the client!
RE:
Any news on this topic? As it is under review for quite a time?
RE:
I agree that there should be something in place to prevent this from happening
RE:
I agree that there should be something in place to prevent this from happening.
RE:
Great idea. So many customers inadvertently submit. More robust checks and control required.
RE:
Implementing unnecessary functions can not only lead to inefficiencies but also create significant challenges in day-to-day operations. It is crucial to establish a setup where the benefit for one legal entity is achieved without imposing undue burdens or negative impacts on other legal entities. Flavio Bass, Business Engineer Operations.
RE:
Hello,Could you reconsider to add this functionality to MS D365FO Roadmap? Our manufacturing customers need this functionality.Thank you,Sergi
RE:
The Electronic Signature function can save a lot of time and steps in a process and is therefore a must.We have several companies on the system (engineering, production and trading companies) with different compliance requirements, therefor it's an absolute requirement for us to set up this function based on the legal or, even better, on the operation unit.Compliance requisitions are following the product process, and if i have the product or process not in this company than the use case is not necessary.SincerelyNorbert Hoch, D365 suppliy chain management manager and system administrator
RE:
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.
RE:
Is there any timeline by when this will be implemented?