Announcements
No record found.
Hi there,
I'm having a requirement to expose the data we're seeing in Trial balance, so could you provide your assistance on how to create the custom entity with relations so that we can able to expose the data's for below headers we're having in TB reports?
Hi Vignesh,
Trial balance report will run once you provide a value for date, financial dimension set and posting layer.
You have possibility to create this report in your reporting solution (e.g. PowerBI) by exporting data from standard entity "General journal account entry" or "General journal account entry reporting".
Hi Alireza,
Standard entity 'General journal account entry' public visibility is 'No', hence i'm trying to create the similar type of custom entity and making it public 'yes', need assistance on how to compute the opening/closing balance values as like we're getting in TB reports and make it available through custom entity expose.
Any input on this?
Opening/closing balance can be calculated dependent on date and financial dimension though it can have dynamics filter. Once you export data from LedgerJournalAccountEntry to your AzureSQLDB you have possibility to build a cube to calculate trial balance based on specified date and financial dimension.
Do you want to create a custom entity by hard coding date interval (e.g. Trail balance 2021)?
We're implementing OData integration and hence creating custom entity for Trial balances, so i'm trying to define relations and compute the opening/closing balances on entity level
Like you mentioned already GeneralJournalAccountEntry entity is not public so you can not access it via ODATA, while you can make copy of this entity (i.e. create a custom entity) and make it public in order to use it for reading via ODATA.
Please check the following post from Microsoft docs on how to create a custom entity and use standard OData syntax to retrieve data
docs.microsoft.com/.../build-consuming-data-entities
docs.microsoft.com/.../create-entities
We already done with creating custom entity and can able to retrieve data from outside FO through OData call, challenge is we don't have direct field for opening balance and closing balance and hence we can't expose it, so we need to create computed field which should show the opening/closing balance and credit/debit details as we're seeing in TB reports, so need assistance in defining the required relations between datasources to achieve this.
I think that you may need to create a custom entity for your purpose by adding formula to calculate balance and then you can add query call when you get data from the entity.
I recommend to add a cube in your reporting solution to calculate trail balance than via OData entity so the user can decide over date interval or/and financial dimensions.
Have you tried to use filter expressions in OData URIs?
docs.microsoft.com/.../use-filter-expressions-in-odata-uris
Could you guide how to add cube? can we add this custom entity level?
As an example, you can try to use standard entity "General journal account entry" from D365FS to AzureSQLDB and then connect PowerBI to AzureSQLDB to get the data.
Please check following post from Microsoft docs on how to create a cube:
docs.microsoft.com/.../walkthrough-creating-a-cube
docs.microsoft.com/.../walkthrough-displaying-cube-data-in-a-report
docs.microsoft.com/.../walkthrough-analyzing-cube-data-in-microsoft-sql-server-management-studio
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.
Congratulations to our 2026 Super Stars!
We are thrilled to have these Champions in our Community!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Giorgio Bonacorsi 692
André Arnaud de Cal... 532 Super User 2026 Season 1
CP04-islander 478
