Within D365 Finance & Operations we need to add a custom field to invoices, purchase orders, journal postings and ledger entries to hold an identifier (Job_id) from another system.
How can this be done without affecting upgrades?
We want the field to be visible and editable on the relevant screens, and flow through to reporting, queries, and ideally APIs.
Perhaps there are predefined custom fields already on these entities for customers to use as they choose? It seems strange that Microsoft has not enabled some level of flexibility for customers to add some client specific info easily to these entities.
If you can add them then how do you do it without coding ideally, so that upgrades are not impacted and ideally you dont have to regression test anything?
Any ideas from anyone on how we could solve this without breaking the ERP would be most appreciated.
The F&O is extensible. Developers can easily add fields to standard tables, expose them to forms, entities (= for import/export, OData, Power Platform) and so on.
But note that if you also want a flow of data in certain business processes, you'll also need code extensions to extend the business logic. But before developers can do that, you need to define the requested behaviour. For example, if an invoice contains multiple orders and these orders don't have the same Job ID, what job ID do you want to have in the invoice? You need to think about this type of things...
Was this reply helpful?YesNo
Under review
Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.
4
Share
Report
All responses (
Answers (
