on
RE:
Hi,Thank you for highlighting these challenges around Project Quotation and Confirmation documents in Dynamics 365 — this is a common pain point we’ve seen across many implementations.Interestingly, Visionet has already addressed these exact gaps with our Customer Quotation Management Accelerator for Dynamics 365 Commerce (B2B).Our solution is purpose-built to simplify and enhance the quotation management process — both from a backend (BDM/documents) and frontend (customer experience) perspective.Here’s how our solution directly addresses your concerns:→ Separate Document Templates for Quotation & Confirmation:Unlike the standard project quotation flow where the same BDM document is used for both quotation and confirmation, our solution fully supports separate templates — just like Sales Quotation and Confirmation — allowing businesses to differentiate documents easily with different titles, formats, and messaging.→ Enhanced Document Translation Support:We’ve optimized document generation to fully support runtime translations — ensuring that multilingual customers receive correctly localized documents every time.→ More Data & Notes Availability:Our solution extends the standard data model, exposing additional tables and fields for BDM. Plus, you can easily configure form notes and custom sections as needed to enrich both quotations and confirmation documents.You can explore more details about our solution here:🔗 Visionet Customer Quotation Management Acceleratorhttps://appsource.microsoft.com/en-us/marketplace/consulting-services/visionetsystems.quotation-management-accelerator?search=quotation%20management&page=1&tab=Overview&country=US
RE:
This has been a sever limit not only for the invoice capture app but also other models using AI Builder. Without the ability to move models between environments it is severely limiting because we need to train models in test environments before moving them to production.Additionally, when we refresh our UAT/Sandbox or any other environment we need to completely retrain the model. This takes a significant amount of time and causes us to limit our use cases to the highest volume and highest value because it take so long to retrain our test environments.
RE:
I'm in favor of this idea. The remit-to address should function consistently, including when the requisition worksheet is used.
RE:
Please add asap. User did Edit in Excel not really knowing what they were doing and deleted all GL accounts even though trxs were posted to those accounts. Need to allow Open in Excel on pages and to use Send to Excel for reports for all users, but only allow Edit in Excel permissions to certain users. The permission to edit in excel is included in so many permission sets which needs to be removed and be a separate permission set to assign or not assign to users. Edit in Excel permission set should actually relate to edit in excel feature.
RE:
If you can't update the search feature to be less clunky, really the other option is update to a "Save as" feature that when you are on or select a template it respects that selection to create a new copy. Try it, just search for a newly created template and see all the existing templates that get in the way and you can't easily select that template you want to copy. Thanks for trying this from the customer's shoes and issue will be apparent I promise.
RE:
This will be an extremely useful featureIn its absence, it would be very challenging to implement the custom invoice model
RE:
My customers needs this. Is there a cause, why it is still not possible?
RE:
I am sure this feature was working in AX2012 as we have used it extensively in previous implementations. It would be great to see it back.
RE:
Fully agree with the comments below — it's difficult to understand why kilometers are still not supported as a default unit of measure for mileage expenses, especially considering that over 90% of the world uses the metric system.As someone working on global D365FO implementations, we constantly need to build workarounds or customizations just to support basic regional needs like this — whether it's in Expense Management or Transportation Management (TMS), where miles are also still hardcoded in the standard mileage engine.If Microsoft wants Dynamics 365 to be a truly global solution, it’s essential to start addressing these long-standing requests. This idea has been here since 2019, yet still hasn’t moved forward.Please prioritize metric system support — it’s not a feature request, it’s a localization necessity.Elise De Brie
RE:
Resolved in release wave 1 2025