Skip to main content

Exposing Dimension and Dimension Values in General Ledger Entries

 

Introduction:

Ever felt a need to expose Dimensions on G/L Entries? Wouldn't it be simple to check-in G/L Entries or perform a Pivot in Excel directly?
Well, that is exactly what I'm planning for.

Use Case: Add the 2 Global Dimension  & 6 Shortcut Dimension to G/L Entries Table in Business Central. These fields should be downloadable in Edit in Excel.

Pre-requisites:

  • Microsoft Dynamics 365 Business Central
  • VS Code
  • AL Language Extension

Procedure:

1. Adding fields to the Page:
I will be creating 8 variables on the G/L Entry Page of the Type Code[30] and add the variables as fields to the page.
Fields to G/L Entry Page
Fields to G/L Entry Page

2. Adding Logic to fetch data into the fields:
The fields that were recently created needs to be filled in with values for each and every record.
Dimension Set Entries table consist of Dimension Set ID (Integer) and Dimension Code which will be getting from General Ledger Setup. 

Logic to fetch the Dimension value
Fetch the Dimension Value


Output:

Dimension in G/L Entries 


Exporting to Excel:

Edit in Excel with Dimensions


Conclusion:

I hope this helps you in generating some sort of reporting & analysis directly through G/L.
Possible use of this could be using this page through WebService to generate Data for PowerBI.

Comments

  1. How does this handle a scenario where you are not using all 8 shortcut dimensions? Would it be considered worthwhile to have a Visibility variable set for each column and then use that to also set the data in the data variable?

    ReplyDelete
  2. Dear Olister

    Thanks a lot for this great topic,

    How to change the caption of these new fields instead of Dim1, Dim2 to get the caption in the General Ledger setup like Department, Project & etc.

    Thanks a lot

    ReplyDelete

Post a Comment

Let me know your comments below. I'll try my best to answer your comment

Popular posts from this blog

Something went wrong. An Error occurred - Error Resolution

Introduction: With the installation of NAV 2018 or BC On-premise, I have observed that when creating New Server Instance and New WebServer Instance, you will get the error 'Something went wrong. An Error occurred '. I referred to the community questions below but didn't find my resolution. Hence, I decided to write this blog. Pre-requisites: Microsoft Dynamics Business Central - On-Premise / NAV 2018 Understanding of Business Central Authentication  Books & References: https://community.dynamics.com/nav/f/microsoft-dynamics-nav-forum/261301/nav-2018-web-client-an-error-has-occurred https://community.dynamics.com/business/f/dynamics-365-business-central-forum/421987/error-something-went-wrong-an-error-has-occurred-azure-ad-tenant Demonstration: 1. Creation of NAVServerInstance: In order to create NAVServerInstance, you can either add the Server Instance through Business Central Administration or Powershell command. Add Instance - Business Central Administration Add Insta

Universal Code Error and Resolution

Introduction: On Friday, May 12th, 2023, the Business Central On-Premise Production Environments started throwing universal code errors as follows. This occurred to every customer on a lower version of BC 19,20 and 21 irrespective of their localization, customization, and license. Pre-requisites:  Understanding of Technical Upgrade in Business Central On-Prem References: BC20 On prem. Universal Code requirement error after installing customer's license. - Dynamics 365 Business Central Forum Community Forum (40) Yammer : Dynamics 365 Business Central Development : View Conversation Root Cause: The certificate that signs Microsoft Base Application was expired. Errors started occurring if you Uninstalled, Installed Extensions, Restart Server Instances or for some even out of random started popping out. We first thought could be a license issue as we had fixed that before but this did not solve the issue. Resolution: Microsoft identified the issue and posted the following update The mi

How to resolve 'Edit in Excel' issues

  Introduction: As you know that D365 BC offers Edit in Excel functionality. But manipulating or customizing such a  standard functionality is difficult as there is not much control available. Hence, solving issues is also a difficult task. I will be resolving the issue for this specific issue, however, the debugging steps are similar. Pre- requisites : ODATA V4 Connectivity tool for Webservices Microsoft Dynamics 365 Business Central Books & References: https://community.dynamics.com/business/f/dynamics-365-business-central-forum/448226/issue-with-excel-add-in/ Demonstration: The way Edit in Excel works is that for a given page a Webservice is created adding PageID and Page Name. Hence, there are some Webservice connectivity checks in place to validate. 1. Edit in Excel Custom Action on the page: If you are adding Edit in Excel Action on the page, please ensure that you are providing appropriate PageName and Filter criteria as Webservice is using these parameters Refer Editworkshe