Ability to run Document Routing Agent as a service for more than 90 days
The document routing agent requires for an Azure token to be generated every 90 days in order to remain operable according to the documentation (and subsequent follow up discussions with Microsoft Support to confirm this), to keep the service working requires several manual steps to be perform...
Security framework update: back-end is inconsistent with the front-end
Changes done on the security type permissions on a visual studio privilege has a different result then changes done on the front end.
The idea would be to change the properties in visual studio on the security object type. We now only have one field with the enum read/update/delete/... I...
Incremental refresh for Entity Store
Entity store has been designed as a data warehouse. The refresh option of entities is provided as a full reset, which means that during refreshing the data is uploading all records again. This takes a lot of time, especially for the organizations having huge amount of data. This is why the increm...
Improved support for single-tenant multi-instance scenarios for F&O
In our large, decentralized organization, we use Dynamics 365 as the ERP/CRM for smaller entities. These tend to be independent from each other, and each thus wants its own D365 F&O instance which it can customize as needed, and has no requirement to share data with its peers. Consequently, in LC...
Ability to restrict Network Printers
Currently Network Printers created in Dynamics 365 for Operations are available to all users of an organization for which the printer is setup for. Certain printers such as check printers should be restricted by user or group. In the past this would have been done by Active Directo...
Batch delegation of workflow items
When a user leaves or is on annual leave the systems adminstrator needs to delegate workflow items to an alternative user. Whilst all new items can be setup to automaticaly delegate existign workflow items need to be delegated 1 item at a time. It woudl be beneficial for the system adninistrator...
Show which user has enabled a feature in feature managment
We recently had the problem that one user activated several features by mistake. To find the corresponding user we had to use the TableBrowser for table FeatureManagementMetadata, but it would be much better if we could see this directly in the feature management workspace.
Extend client session timeout per users
A partner requests the feature to specify client session timeout period per user.
Currently session timeout period is 1 hour. And user cannot change it.
They request that end user can change the client session timeout period.
For example, at User Options>Preference form.
Expand All - Collapse All Option for the "Grouping in Grids" feature
This is a wonderful feature that has a lot of promise, but the issue is when it's loaded, by default every group is expanded. Typically, the benefit of collapsing groups is to see the summarized view of a large table, and only expand the ones you need to see. If you have thousands of records, g...
Batch Job - adding task - filter/sort for “class name” (performance)
When adding a task to a batch job manually you must wait quite long time for the lookup “Class name”. To improve performance and handling there should be the possibility to filter and sort. In the “Active Document Tables” there is a filter/sort for the “Table name”. The same functionality for ...
Administrator
By default, the network printer list in D365F&O applications is filter based on the active Legal Entity. For cases where it is necessary to enforce corporate access policies beyond legal entity constraints custom extensions will be required. We encourage partners & ISVs to deliver a custom solution using the collection of class delegate handlers for the print destination settings form. These methods are used to override the default experience when interacting with the Print Destination form. For example, you can use these methods to filter the list of available network printers displayed to the user at runtime or pre-select the default printer based on user context information.
Use the following delegate to introduce custom logic to filter the list of network printers based on session context:
public class SRSPrintDestinationSettingsDelegates
{
/// <summary>
/// Delegate for building printer combobox control on the form.
/// </summary>
/// <param name = "deviceList">Printer combobox control on the form.</param>
delegate void buildPrinterComboBox(FormComboBoxControl deviceList) { }
}