Dynamics 365 Business Central – Removing access to pages such as the Chart of Accounts Page

Introduction

There might be instances where you want to remove a users access to certain pages in Business Central. This blog walks through how to achieve this by creating a new permission set and utilising the “exclude” feature, using the Chart of Accounts page as an example.

The User

The user below has been configured with a standard full access permission set, which is fine, however I want to remove the permission to the Chart of Accounts page.

I therefore go to “Permissions set” and create a new permission called “FULL ACCESS NO COA” as per below

I then add the old D365 BUS PREMIUM permission set to this, and exclude the Chart of Accounts page

Finally, I go back to the User page and remove the “D365 BUS PREMIUM” permission set and replace with the newly created “FULL ACCESS NO COA” permission set

Now the user can no longer see or search for the “Chart of Accounts” page

Conclusion

This is an easy way to remove access to certain pages in Business Central. Hopefully it will help someone in the future.

Thanks for reading!

Need help with Business Central. Contact us

Dynamics 365 Business Central – Message “There is nothing to post because the journal does not contain a quantity or amount” when posting a Recurring General Journal

Introduction

When attempting to post a recurring general journal you receive the message “There is nothing to post because the journal does not contain a quantity or amount” even though you have specified the General Ledger codes and the amounts and everything appears fine.

This is a common query that crops up, and also something I see from time to time in the forums, so I thought I’d write it up for reference and to hopefully help anyone else who receives this message.

The Recurring General Journal

Below is a recurring general journal. I’ve populated all the required fields however when I try and post it I get the message below:

The Solution

The reason I’m getting this message is because of the unique way in which a recurring general journal works. In a Recurring General Journal the “Posting Date” is compared to the “Work Date” and if the posting date is greater than the work date you receive this message.

I’ll therefore compare the Posting Date on my journal to my Work Date, and as you can see the Posting Date is in advance of my Work Date:

Therefore, in my case, the solution is to change the user date to a date of 01/01/23 (or a date in advance of 01/01/23) and try again:

After doing this my journal will now post 🙂

Conclusion

As far as I’m aware, this is the only journal that behaves this way. For example, I can post a General Journal and the system won’t check the Work Date against the Posting Date.

I suspect the primary reason for this behaviour is to prevent a user mistakenly posting a recurring general journal numerous times, as by default the lines remain on a recurring general journal after you have posted it, and the posting date automatically advances based on the “Recurring Frequency”. (i.e. if the recurring frequently in 1M the Posting Date changes by one month).

Therefore you could post the journal once and then post it again by accident. Having the system perform this simple check prevents this.

Thanks for reading!

Dynamics 365 Business Central – Walking through an Adjust Exchange Rates (revaluation) scenario in Business Central

Introduction

Recently I helped someone in the Business Central forum with a query on revaluing their bank accounts using the “Adjust Exchange Rate” batch job.

We went back and forth for a while, trying various things, however in the end it was resolved by providing a simple worked example of the whole process that the user could compare to their process.

Therefore I thought it might be useful to write this up for anyone else who may have similar issues and want to see the whole process in action. (and as a bonus I can also use it as a reference point in future 🙂 )

** For info the original forum post can be found here

The Scenario

In this scenario my local currency (LCY) is GBP and I have a EURO bank account with several transactions that I wish to revalue at month end using a rate of 1.5.

Step 1 – The initial transactions

To prepare for the revaluation I need some transactions on the EURO bank account. Therefore, I’ve posted the three entries below using different exchange rates.

The transactions total €600 with a LCY amount of £516.

Step 2 – Set the month end rate

Next, I set the month end rate of 1.5 in the Currency Exchange Rate page. This is the rate I want to revalue the bank account ledger entries at the end of month.

** For more info on how to set exchange rates, and what each field in this page means, I wrote this blog post.

Step 3 – Run the “Adjust Exchange Rate” batch job

Finally, I run the “Adjust Exchange Rate” batch job with a posting date of 30/11/22 and added a few additional filters to revalue the bank account ledger entries.

Step 4 – The Results

The system should create an adjustment of £116. This is because the bank account ledger entries total €600, which when revalued at the new rate of 1.5, equal an LCY amount of £400, and the current LCY amount is £516. Therefore an adjustment of £116 is required.

If we look at the General Ledger entries the Exchange Rate Adjustment has created, we can see this is exactly what has happened.

The system has also created a bank account ledger entry to record the exchange adjustment

Conclusion

The “Adjust Exchange Rate” batch job is an essential tool for companies that post transactions in foreign currencies and wish to revalue their customers, vendors and bank accounts.

However, one limitation to the routine is the inability to revalue an individual GL code, which some companies may find an issue, especially if migrating from Dynamics GP which has this functionality as standard. This is because only the LCY amount is held on the General Ledger Entries. (as well as the reporting currency which is something a little different)

Hopefully this functionality will be added in a later version of Business Central :).

Thanks for reading!