Hello.
In Dynamics 365 F&O, on the purchase order confirmation screen, there is an option to print the purchase order. However, the standard template does not meet the business requirements, since I need to add more information, company logo, and customize the layout.
I would like to understand how this process works natively using Electronic Reporting (ER).
My questions are:
-
Can I customize the standard Microsoft template, or is it recommended to create a derived/new format?
-
How does the structure work in ER for documents with header and lines, such as purchase orders?
-
If I learn this process for purchase orders, will I be able to apply the same approach to customize other documents in Dynamics 365 F&O as well?
-
Are there any recommended learning channels, documentation, courses, or best practices for learning Electronic Reporting development in Dynamics 365 F&O?
Thank you in advance.
Hi @Maria_Alice_Santana
ER is pretty straightforward once you get the hang of it.
Customize or create new? Copy the standard template and create a derived format. Keeps your stuff separate from Microsoft updates.
How does ER work? Two parts: a data model (what data you pull) and a format (how it looks). For POs, the model connects the header to line items. The format binds those fields to your template.
Works for other documents? Yes. Invoices, receipts, and delivery notes, the same approach for everything.
Best way to learn? Hands-on. Copy an existing template, tweak a few fields, and print it. You’ll figure it out.
Common stumbles: Most teams get tripped up on data model binding and pulling company info like logos. We see this all the time.
You can definitely learn this yourself, or we can walk you through it and get you up to speed in a day or two. Let us know what works for you.
Olá .
Estou com dificuldades no mapeamento do modelo de dados e gostaria de receber alguma orientação.
Criei uma fonte de dados raiz, adicionei a tabela e ela possui relacionamentos existentes.
Ainda preciso adicionar e vincular manualmente essas tabelas relacionadas no mapeamento do modelo de dados?
Hi @Maria_Alice_Santana
If you’re using tables as data sources in ER, the existing table relationships are not always picked up automatically. In many cases, you’ll still need to add the related data sources and define the links in the model mapping, especially when working with header, lines, company information, or logos.
A quick check is whether you can already access the related fields from your root data source. If not, you’ll likely need to add the relationship manually.
If you’d like, share a screenshot of your model mapping, and I’ll be happy to point you in the right direction. We work with ER quite a bit and can help if needed.