Skip to main content

Bug in NAV / Business Central when Cancelling Posted Sales Credit Memo


Introduction:

With the evolution of Microsoft Dynamics 365 Business Central from Microsoft Dynamics NAV, many of us did not get the chance to completely explore Business Central to its entirety.
One such bug that I found in Business Central is when you Cancel a Posted Sales Credit Memo, system throws an error. Let take a closer look at the bug.

Pre-requisites:

Microsoft Dynamics 365 Business Central
Microsoft Dynamics NAV

Demonstration:

When Cancelling a Posted Sales Credit Memo, the error I get is
 'The General Posting Setup does not exist. Identification fields and values: Gen. Bus. Posting Group='DEFAULT',Gen. Prod. Posting Group='''



When I created a General Posting Setup with Gen. Business Posting Group as 'DEFAULT' and Gen. Prod. Posting Group as '' I get an error 
'Gen. Prod. Posting Group must be filled in. Enter a Value.'



This in not only related to Posted Sales Credit Memo but all the Financial Documents that do not use Gen. Product Posting Setup.

Also, to verify I had tested creation of General Posting Setup with Gen. Prod. Posting Group as BLANK and it was successful.


Conclusion:

With confirmation from Microsoft Support, they have officially declared this functionality as bug.



Comments

Popular posts from this blog

TIP: Working with changing Field DataTypes and Deleting fields in Business Central

Introduction:
Imagine a scenario where as per the requirements provided by your clients, you have set up the Database structure in NAV/Business Central.
Then comes a requirement in Phase 2 which completely redefines the database structure which was provided by you and you need to delete a few fields in a table and move it to another table.

Pre-requisites:
Microsoft Dynamics NAV
Microsoft Dynamics Business Central

Books & References:
https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/properties/devenv-obsoletestate-property

Solution:
1. In Microsoft Dynamics NAV, there was a flexibility to delete fields, tables, and keys and using  Force-Sync, you can directly delete the field, table, and keys from SQL Database.


2. Whereas in Microsoft Dynamics Business Central, you cannot delete the fields, keys, and tables.
In order to deploy this deleted change, you need to mention this field, table, and keys with Obsolete State Removed.


After you mention the field as…

How to actually use Profile Objects in Business Central

To 'Whomsoever This May Concern',
When I was working on a Production Deployment for one of my clients, I noticed that I could not create a Profile in Business Central Production Tenant. I was able to create new Profile in Sandbox.


Then I tried using configuration Package and modify the contents of 2000000178 Profile Table and as always configuration package blocked it.



There was no way of dealing with this other thancontacting Microsoft Support and this is the answer I get from a Support Engineer

I was on the verge to give my clients a link pointing to a specific page i.e https://businesscentral.dynamics.com/?page=50150

After being a little creative, I figured out that developing profile objects might help.

And this resolved this issue for me.




Permission Issues on Posting after deploying Extension in Business Central Production Tenant

Introduction:
Issues when you deploy your app in Business Central Production VS Business Central Sandbox. Let us what are the implications of the statement.
In my last blog () I have already pointed out the difference in Profile as to how can create new Profile in Business Central Sandbox but the same is not possible in Business Central Production.
Pre-requisite:
Microsoft Dynamics Business Central (SaaS)
Demonstration: 1. I was working with General Journals after deploying the App in Production Environment. Suddenly during posting I go this error.


2. To Verify this issue is not of Permission Set, I gave the User SUPER Permission and tried again.

I got the same error despite giving SUPER Permission. Again the same the error, so I checked the Effective Permissions.

I noticed that Table G/L Entry has an Indirect Permission. I replicated the same Production in Sandbox. But I didn’t find any issue like this.

3. Moreover, I noticed that when I uninstall the App, the Production works perfectly and …