Dynamics 365 Finance and Operations Cross-Apps

Customers who are using Dynamics 365 Finance and Supply Chain Management apps are unable to use follow-me printing and secure printing with the Document Routing Agent (DRA) instead they have to print to PDF and then send to a printer. This does not present a very good user experience to the end users. 

The expectation is that once Universal Print is integrated into Dynamics 365 Finance and Supply Chain Management apps our customers will be able to use it, in a more user-friendly manner while also using follow-me printing and secure printing.

This is a pain point for our customers.

Link to copy of idea posted in Tech Community:

Integration for Universal Print and Dynamics 365 Finance and Supply Chain Management apps - Microsoft Tech Community

Via virtual entities Dynamics 365 Finance and Operations (FinOps) data could be displayed in grid view in Dynamics 365 Customer Engagement (CE). Decimals are always displayed with 6 digits after the separator (e.g. 365.220000). 6 digits are confusing users when decimal amounts are displayed in CE. For Euro countries typically decimal precision point 2 would be more suitable (e.g. 365.22), for other geographies this may be 3 or 4. The decimal point precision could be configured to less then 6 in FinOps but it is so far not applied in grid view within CE apps, such as Customer Service Hub. Request is to provide the option to set decimal point precision to less then 6 for FinOps decimals and display accordingly in CE.

When setting up roles and access, we often see that menues and menu items a user don't need is visible in the menu.

There are two asks to this idea:

1. Make it possible to add personalizations to menues to show/hide menu items. This way a user can hide things he have access to, but don't want to see. This create a more lean and easy to use menu structure.
2. In favorites, please add the concept of "folders", so that users can create a hierarchical favorites structure.

Thanks

Right now, all DLL dependencies (.NET assemblies) in a D365 package get loaded into the same process space as the whole AOS server. This has several drawbacks as it leads us in a DLL hell. If a DLL is included by the AOS or any default package, one must not add another version of the DLL, especially since it is often undefined, which DLL gets lucky enough to get loaded first. This kan wreak all kind of havoc, as the problems are not always reproducible.

This is especially critical with some of the Azure standard DLLs deployed by the standard. If - for whatever reason - you require another (mostly newer) DLL instead, you can't do so (usually leading to Azure Function micro-services or similar constructs).

Beyond that, if you have two ISVs with contradicting dependencies (been there in the past), you are at the whim of the ISV distributors to unify their packages to a compatible dependency version.

As a solution, custom DLL dependencies could be isolated in AppDomains. As a primary solution in .NET to isolate applications or extensions from each other, the AOS should formally support this. Ideally, all non Microsoft packages should use such a mechanism to avoid conflicts (you could check this in ISV / AppSource validations even).

While I'm aware that we can do this at the C# level ourselves, it is a rather deep change we would be doing there. Thus, a standard approach to introducing a new AppDomain with a depending assembly would be important, plus enforcing AppSource packages to use this.

Having the AOS kernel team support this, is therefore paramount.

In a perfect world, there would be an automatic proxying between X++ code and DLLs in their AppDomains.

When searching through inventory in the On-hand list, it would be beneficial to have visibility of the expiration and manufacturing dates of the batches on the same screen. Presently, in order for users to see this information, it requires them to click into the hyperlink of the batch number.

Today it is not possible to auto-publish a certain user personalization to new uses in D365FO that will be added in the future. You can only copy this to the users that is already in D365FO.

We would like it to be possible to do this in the same way as we publish views to certain security roles, so that the user personalization we have set up to be published will automatically be the default personalization for the new users in the different security roles.

It would be extremely helpful if the legal entities in which a Product has been released into were visible within the Products and/or Released Products table.

SQL disconnections are expected in a SaaS environment, as indicated in the following doc:

https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/sysadmin/retryable-batch#retry-the-batch-job-task-when-transient-sql-server-errors-occur

"Currently, if finance and operations apps experience a brief loss of connection to Microsoft SQL Server, all batch jobs that are running fail. This behavior disrupts business processes. Because connection loss is inevitable in a cloud service...."

Sometimes, this kind or disconnections are happening during working hours and the users get different errors, so it should be very interesting if we could send them a message or notification to the administrators indicating that we had a short SQL disconnection and the duration to avoid any misunderstanding regarding the issues.

With version 10.0.29 Microsoft gave the opportunity to save workspaces the same way as with filter views. At the same time they restricted the possibility to copy personalizations, such as a workspace, to other users.

Since it is not possible to save a personalized dashboard as your own, it will always be defined as a 'Standard view'. This creates a problem when you want to have links attached to a workspace (with or without counting) and share it with other users.

A solution for this would be to personalize your own dashboard, by removing/adding workspaces you want to have and then save it with a new name. The same approach as you would do with a filter view and a workspace.