Hi Everyone!
I need to read tables that are not exposed in the data entity. How do I do this at D365FO?
I already have a connection through Odata
Thank you
You have to create data entity for those tables and make sure to set is public property to yes in Order to access those entities using Odata. Remember its not a good practice to enable large transactions tables using such a method.
How can I do this? Is it on the D365 or Azure portal?
Thanks for de help.
You have to develope entities in visual studio . Take a look at below link to see how you can build those. You /Your developer need 1 box dev VM to build a custom entity.
docs.microsoft.com/.../build-consuming-data-entities
Last question ... Is there another way to do this? I need to read the invoice data and accounting data
You need to create entities in order to expose data using ODATA. Which invoices you are looking for ,customer or vendor ? Customer /Vendor invoice tables does not have any data entity, so you have to create one.
Another way is using BYOD where you can export data to your own azure SQL DB but there also you need to develope entities if standard entity is not present.
May I ask what is your business requirement ?
I am Brazilian, and I need all the Invoices (Customer and Vendor) to comply with the Brazilian legislation, but for that I need to integrate all invoices into my system. In the AX2012 version I read the database, but my client migrated to D365FO, i am a developer, but I don't implement D365.
I can read the entities, but only those that are available, but are not enough.
For customer and vendor invoice tables(CustInvoiceJour and VendInvoiceJour) there is no out of the box entity is present so you have to develop one, once you build entity you have multiple options like using BYOD to export data you want to your own azure DB , you can use data management package API, use flow or logic apps to read data from those etc.. Use link i shared above to develop entity. If you want to fetch data from multiple tables , i would suggest you to create different entities instead of creating one large entity.
data entities is a good option
also could look for ER electronic reporting to extract data
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.
As AI tools become more common, we’re introducing a Responsible AI Use…
We are honored to recognize Abhilash Warrier as our Community Spotlight honoree for…
These are the community rock stars!
Stay up to date on forum activity by subscribing.
CA Neeraj Kumar 2,167
André Arnaud de Cal... 867 Super User 2025 Season 2
Sohaib Cheema 617 User Group Leader
