-
Custom Views - Dropping while creating new Purchas Order
Suggested by Mohammed Sohail – New – 0 Comments
Custom views applied on the form purchase order list page gets dropped when new button is clicked for creating a new record, however in Sales order list page this behavior is not observed - the custom views on the form remains as is when new button is clicked and record is created.
We suggest that purchase order list page should not drop its custom filters when new button is clicked and should behave similar to Sales order list page.
If we can do this change users will be hassle free while creating orders as for now whenever they are creating a new PO they need to re-apply their saved filter.
-
Invoice Match price Totals Tolerance - Currency Type
Suggested by Ps Praveen Kumar – New – 1 Comments
According to the standard functionality set by MSD, the system takes into account the currency for Match price total tolerance based on the Match currency type field.
However, the business requires that invoice matching be conducted based on Transaction currency, while Match price totals tolerance should be determined based on Accounting currency.
Considering the aforementioned business case, It is beneficial for businesses to have the option to select the Match price total tolerance based on either the Accounting currency or the Transaction currency, rather than having the system automatically choose the field from the Matching currency type field.
-
Customer invoice settlement based on amount in Bank module
Suggested by Davio Verlinden – New – 0 Comments
Many customers ONLY want their customer payments to be automatically settled IF the amount on the bank statement line = to the (sum) of amounts of the referenced invoice(s). Same as with SKG isv. However, current functionality does not support this idea. It can only automatically settle based on amount if only 1 invoice is referenced by the customer, but this is not common as most customers pays multiple invoiced at once. Theoretically, you want to use the following logic in the matching rules
- Invoice IN Reference No
- Invoice amount in transaction currency = Amount in transaction currency
The second bullet point is the logic that does not fully work in the current bank module. Current logic will only work if the customer references 1 invoice. When 2(+) invoices are referenced, the rule will not work as it will only look at the first invoice referenced. Meaning, this rule will never correctly settle if customers reference multiple invoices. I want to be able to use this logic for customers who pay multiple invoices at once, as this happens more often. Many clients ask for this functionality.
I would like to see an update in this functionality as I believe this is a flaw in the design.
-
In the Excel Add-In, the design does not include columns to map the fields for project category, project date, and line property
Suggested by Ilse Mendez Nava – New – 0 Comments
When using the Add-In in a vendor invoice journal where the offset account type is Project, it is required to fill in the fields Category, Project Date, and Line Property. However, the design does not include columns to map these fields.
-
Enable Shortcut Execution for Task Recorder Scripts in Dynamics 365 Finance and Operations
Suggested by Michael Gbadebo – New – 0 Comments
I propose adding a feature in Dynamics 365 Finance and Operations that allows users to create a shortcut (tile, dashboard button, or link) to run a Task Recorder script directly.
Currently, users must manually replay recordings, which adds extra steps. A one-click shortcut would streamline common processes like posting journals or updating inventory, making automation more accessible to all users.
Suggested Options:
- “Pin to workspace” or “Create shortcut” after recording.
- Support for browser-based shortcuts or deep links.
This would improve productivity, reduce user effort, and encourage wider use of Task Recorder for everyday automation.
-
Add Native "Query View Builder" for Operational Reporting (e.g., Sales Reports)
Suggested by Michael Gbadebo – New – 0 Comments
Introduce a built-in Query View Builder in D365FO to help functional consultants create operational reports (e.g., sales, inventory, purchasing) without developer or Power BI/SSRS support.
The tool should allow consultants to:
- Select and join standard tables or entities (e.g.,
SalesOrderHeaders,
Customers
). - Apply filters, grouping, sorting, and basic aggregations (totals, averages).
- Export results to Excel or embed them in workspaces.
Functional consultants often need to build custom operational reports but rely on developers or external tools. A native, no-code builder would enable faster delivery of client requirements directly within D365FO.
Benefits:
- Enables self-service reporting for consultants.
- Reduces dependency on technical teams.
- Keeps reporting secure and native to D365FO.
- Speeds up implementations and change requests.
Requested Capabilities:
- Drag-and-drop query builder
- Table/entity joins and filters
- Basic aggregations
- Excel export / workspace integration
- Role-based security support
- Select and join standard tables or entities (e.g.,
-
Enable One-Click Direct Printing for Sales Order Documents in D365FO
Suggested by Michael Gbadebo – New – 0 Comments
Printing documents such as the Sales Order Confirmation currently requires multiple steps, including selecting print destinations and confirming dialog boxes. While Print Management settings allow for some automation, there is no true one-click or automatic direct print functionality available out of the box from the Sales Order form.
Suggested Enhancement:
Introduce a built-in "Direct Print" button on the Sales Order form (and similar forms like Packing Slip or Invoice), which:
- Uses preconfigured Print Management settings
- Sends the report directly to the assigned printer without user intervention
- Supports background printing for performance optimization
- Optionally logs the print action in the document history
This functionality would reduce manual steps, improve warehouse and sales team efficiency, and align D365FO with common ERP expectations in high-volume order processing environments.
Business Impact:
- Saves time in high-volume order processing scenarios
- Reduces user error by standardizing print behavior
- Encourages further automation without the need for custom development or third-party ISVs
-
Electronic Invoice PDF files cannot be downloaded in bulk - Mexican Localization
Suggested by Eric Zavala – New – 0 Comments
Currently, when using the Mexican Localization feature, it is not possible to download more than one e-invoice PDF file in bulk. Since it is very common for customers to request the sharing of e-invoice history, the only way to obtain them is to download each invoice individually.
Ideally, there would be a menu where it would be possible to specify the range of e-invoices to download, either by ID or by customer account, to facilitate the necessary effort.
-
Electronic Invoice PDF and XML files should be sent to the customer on the same email - Mexican Localization
Suggested by Eric Zavala – New – 0 Comments
Currently, when using the email functionality for electronic invoice XML and PDF files in the Mexican Localization, two separate emails are generated for each file. Since most clients process both XML and PDF files for saving to their databases, generating two separate emails for each file can cause confusion.
Ideally, both XML and PDF files could be sent in a single email.
-
Electronic Invoice PDF file name cannot be modified - Mexican Localization
Suggested by Eric Zavala – New – 0 Comments
In Finance, when using the Mexican localization, it is not possible to parameterize the way the name of the electronic invoice PDF is created. Since invoices are sent to the client, a suggestion for parameters that could be included in the name is the following:
Issuer's RFC – The tax identification of the company issuing the invoice.
Invoice number – The unique invoice folio.
Issuance date – In YYYYMMDD format (year, month, day).
Document type – May include labels such as Invoice, Credit Note, etc.
File extension – Usually .pdf
For example, an electronic invoice file might be named: MX123456789-Invoice-20250606.pdf