-
Data entity for Purchase return order line to import/export.
Suggested by Susant Kumar Sabat – New – 0 Comments
Unable to import line in returned order for purchase by using data entity
Go to Accounts payable > ALL purchase order > Create a Return order
Use data entity to import multiple for the PO with Return oder (header) created at previous step
Expected result:
System should be able to import return order line
Issue:
Currently none of the data entity is supported to import or export Purchase return order.
Â
Â
-
Setup to automatically update transfer order lines
Suggested by Richard BLANC – New – 0 Comments
For sales orders, there's a well-known parameter called "Update delivery date on order lines" that controls whether changes to the header delivery date should cascade to the lines. However, transfer orders do not have an equivalent out-of-the-box parameter to control this behavior.
Could you add it please?
-
Improve Zip Code Matching Logic in DMF to Auto create reference of postal code on customer address to Zip/postal codes master data when customer addresses are created using data management import
Suggested by Deepti Dadheech – New – 0 Comments
When importing customer master data addresses using Data Management Framework (DMF) via Data management > Import, the system currently links the zip code on the customer address to the first found zip code when the same zip code ID exists multiple times with different street number ranges.
Issue:
- This behavior can lead to incorrect zip code associations, especially in regions where multiple zip codes cover overlapping areas but differ by street number ranges.
- Instead of intelligently matching the zip code based on the street number of the customer address, the system requires the user to manually select the correct zip code ID based on the street number of the customer address which is impractical and inefficient when dealing with large volumes of customer data.
- Although the out-of-the-box solution allows zip codes to be categorized as odd/even/all street numbers with a defined range, it does not support correct associations automatically resulting in compromised data accuracy.
Proposed Enhancement:
DMF import logic should be updated. Additional criteria of street number matching should be included.
Benefits:
This would ensure a better alignment with regional postal code standards, data accuracy, accurate geo coordinate validations and improve downstream processes like tax calculation, delivery routing, and compliance.
-
Themes - possibility to choose 'dark mode'
Suggested by Camilla Laustsen – New – 0 Comments
We've received feedback from several users who prefer using 'dark mode' in other Microsoft applications, as they find it easier on the eyes—especially during extended periods of use. Given this preference, we wanted to suggest considering the addition of a 'dark mode' option in Microsoft Dynamics.
We believe this feature could enhance user comfort and accessibility, aligning Dynamics with the broader Microsoft ecosystem and user expectations
-
All purchase order form should pull data only active purchase orders by default (not invoiced PO's)
Suggested by Susant Kumar Sabat – New – 0 Comments
Go to Accounts payable > Purchse Orders > All Purchase orders
System is showing all the PO's (open and invoiced PO).
Expectation -
System should show only 'active purchase orders’ by default while opening the form, this will open the form much quicker then currently taking time.
Note: This is inline with standard behavior in All Project form (from Project management) or All free text invoice form ( From Account receivable), they shows only open/active records by default.
-
Update Inventory marking documentation in Microsoft Learn for D365 Supply Chain Management
Suggested by Donald Joseph – New – 0 Comments
Current documentation Inventory marking documentation (Inventory marking - Supply Chain Management | Dynamics 365 | Microsoft Learn) indicates the functionality is default "on" as long as the system is running Supply Chain Management 10.0.36 or later. However, it does not mention costing methodologies disabling the functionality (see Moving average - Supply Chain Management | Dynamics 365 | Microsoft Learn). This should be cross-referenced in the Inventory marking documentation to allow consideration of this limitation.
-
Invoice capture unit price
Suggested by Sarudzai Agenes Midzi – New – 0 Comments
When using the invoice capture app the unit price is not being carried forward to the invoice pending screen generating a blank on the line, the current mitigation to manual entering the value. Please can Microsoft look into this as this is currently the system behaviour
-If qty * unit price == amount, we will transfer qty and unit price to F&O
-If qty * unit price != amount, we will only transfer amount to F&O
-
FO still go on to correct and post invoices dispite the Require the calculated totals to equal the is enabled
Suggested by Sarudzai Agenes Midzi – New – 0 Comments
When an item has a decimal precision set up for its quantity, the system automatically changes it. However, there is an existing setup that prevents the invoice being submitted to workflow automatically if there is a discrepancy in the totals. In such a case the discrepancy needs to be resolved manually and then submit to workflow. Under the purchase ledger parameters>invoice>invoice workflow tab when the Require the calculated totals to equal the is set to yes and despite the warning that the totals do not match the calculated totals in FO still go on to correct and post. This system behaviour may not be appreciated. Please kindly look into it.