Comments
This request aligns with our requirement.In addition to bulk duplication, an important requirement is that the duplicated security objects should be created as new custom Roles, Duties, and Privileges without modifying or impacting the original OOB security objects.The solution should also preserve the full security hierarchy and relationships, including Role > Duty > Privilege relationships and the underlying privilege references.In our scenario, the volume is significant, around 73 Duties and 700 Privileges, so the current one-by-one duplicate option is not practical.The duplicated custom security configuration should also be exportable and importable between environments using a supported Microsoft approach, such as DMF or another supported mechanism.Please consider relationship preservation, custom object creation, and environment migration support as part of this enhancement.
Hi all,I just wanted to bump this once more, because I also believe that this feature is basically mandatory when doing any kind of performance tuning where blocks between different processes are involved.Without it, it is extremely cumbersome to identify the process that holds a lock on a ressource and makes analyzing it a huge timesink.I also wanted to mention that via Application insights, this feature is.. kind of there still? You can get the Callstack of the blocking process, but only if the process that runs into the lock timeout is on the same service tier as the blocking process.In an environment with multiple service tiers this is useless, as we do not know the process that holds the lock, and the sql tracing allowed us to quickly identify the process by simply turning it on and activate the "Debugger.EnableSqlTrace" for all sessions.Best regards,Stefan
As a manufacturing company, we use notes on released products / finished goods to provide production instructions, such as how manufacturing operators should set up or configure specific product features.These notes are sensitive and should only be maintained by the Product Administration team. However, the Manufacturing team still needs to view them during production.Required functionality:Allow security to be configured per Note document type, for example:Product Administration: view, create, edit, deleteManufacturing: view onlyThis should work for Note / Simple note document types, not only file attachments.This would improve segregation of duties, reduce the risk of unauthorized changes to production instructions, and avoid the need for customization around document management.
We need to have the possibility to configure access by document type. We need this especially for document of type Notes (so we cannot use Sharepoint access), where as a customer we are using these notes for product instructions to our manufacturing process. We need to restrict access to view only these notes for a group of users, with edit rights only for administration.This would be great to have!