-
Publish personalization as an admin to a group of users or all users
The personalization options in the application are very strong, limiting the need for customizations while enabling users to simplify their user interface.
A simpler user interface improves the usability and acceptance of the system. It would be great that an administrator (/ consultant) can create the optimal personalization for the forms in use and easily share or deploy this to all users. This limits the need for customizations to hide and change form objects and increases the maintainability.
One of the most heard requests during an implementation is around simplifying these fields. With this option, we can stay away from customizations / code releases and functional designs while quickly helping the new users to adapt to the system.
-
Correct Budget Consumption on Projects for Purchase Orders with a Discount
When a discount is added to a project purchase order with a posting profile main account, other than the main account of the item used, the discount is ignored in the consumption of the related project budget.
This idea is to ensure that the discount is taken into consideration when consuming the project budget to prevent a data inconsistency between the project budget and actual spend.
An example of a scenario that is happening now: A purchase order with a line of 1250 dollar and a discount of 250 dollar (total of line is 1000) is consuming 1250 dollar from the budget while the actual spend on the project is 1000 (and correct). In this case, the idea is that the consumed budget should be identical to the total amount of the purchase order, taking the discount into consideration.
-
The ability to define an e-mail body when sending output documents by e-mail
When sending output documents per e-mail, it is possible to define a subject of the e-mail, but not to define the body. Sending out output documents like purchase orders and sales order confirmations is still very common, but currently we have to send out an empty e-mail, which is often ignored by the recipients or seen as SPAM.
It would be great if we can apply e-mail templates when sending output documents, and influence the output to the body by using variables from the output document, like document numbers, names, addresses and so on.
-
Quick search on customers, vendors and transactions based on ID and direct URL to specific record
Apart from searching for certain forms, it would be great if we could do a search on certain or all entities in the system.
For example by searching for a customer name or vendor ID or product number. Maybe combined with number sequence structures to define what entity you are looking for or by adding a prefix like Customer:######.
It would also be great if we can share specific records using a readable URL on the primary key. Example: &mi=CustTableListPage&Key=#######. Both could be combined in one implementation.
-
Integration between Workflows and Microsoft Flow
More and more workflow approvals need to be gathered from people not using D365fO on a daily basis. Of course we can send out e-mails, but people still have to log in to approve or reject workflows tasks.
It would be great if we can integrate the workflows of AX with the Microsoft Flow approval system, including the ability to share data to Flow on the entity involved (like totals of a PO, quotations details, hour journal totals and so on). In this way we can use all the richness and functionality coming to Flow with Dynamics 365 for Operations as well.
-
Reintroduction of XDS policies / Global Addressbook security
The XDS / Global Addressbook security policies from AX2012 are not available in Dynamics 365. You can enable the policies in code, but only using Overlayering.
These policies are essential to limit access to certain records, certainly when providing access to your environment for vendors and other external parties.
The XDS policies or comparable record level security should be reintroduced in Dynamics 365 or enabling the existing policies should be possible using an Extension instead of Overlayering.
-
Make customer attributes available on receipts
The new customer attributes available on the MPOS are great. It would even benefit us more if we can add these attributes to the receipts via the designer. Some information we capture on the customer record is needed to be shown on the receipt.
I know the new receipt designer is in development. Would be great if this can be added as well. And of course it would be great if order attributes are taken into consideration as well!