Intercompany Transactions Automation #msdyn365bc

Consider using automation tools, such as Business Central's Intercompany Postings functionality, to streamline and automate the creation of intercompany transactions.

Mastering G-L Entry Descriptions in D365 Business Central

Welcome everyone! Today, we're going to talk about an important topic that affects every user of D365 Business Central: i.e., Descriptions in G-L Entry.

Now, you might be thinking, 'Descriptions? That sounds boring!' But trust me, accurate and detailed descriptions are crucial for keeping your financial records organized and up to date. Plus, they can help you avoid costly mistakes and make your life easier in the long run.

Why are G/L Entry Descriptions Important?

Accurate and detailed descriptions are crucial in G-L entry in D365 Business Central. They provide a clear understanding of the purpose and nature of each transaction, helping users track and analyze financial data effectively.

For example, imagine you have two transactions with the same amount: one is for office supplies, and the other is for travel expenses. Without proper descriptions, it would be difficult to differentiate between the two transactions and understand their impact on your company's finances. This could lead to confusion and errors in financial reporting.

 

How to Enter G/L Entry Descriptions?

When entering general journal lines on a page, the system fills in automatically the description field. This description will also be stored in the G/L entry after posting the journal. For a good audit trail, a more detailed description is desirable, when you post a journal line of type G/L Account.

To force the user to enter a more detailed description, it is possible to choose if the system must fill in automatically the description of the G/L account or leave the field blank.

If the Omit Default Descr. in Jnl. Field check box on the G/L Account Card page is checked, the system will not fill in the Description field for that G/L account when selected in a general journal line.

When posting the journal lines, the system will check if all the Description fields are filled in. If there is a blank description, an error message will appear.

 

Note: Leaving the description field blank and checking if all the description fields are filled in before posting, will only be done on the general journal pages in several application areas and on the local Cash Bank Giro pages

 

Best Practices for Writing Descriptions:

Use clear language when writing descriptions. Avoid using technical acronyms that may not be familiar to all users.

Include relevant information in the description, such as the purpose of the transaction or the account being used. This will help other users understand the context of the entry.

Consider the audience when writing descriptions. If the entry will be viewed by multiple users, make sure the description is understandable to everyone.

Be specific and provide enough detail to accurately describe the transaction.

Proofread descriptions before submitting them to ensure accuracy and clarity.

 

How to create a workflow that sends approval requests to more than one user but requires approval from “one of” them

How to create a workflow that sends approval requests to more than one user but requires approval from “one of” them.

How to create custom “business events” in D365 Business Central to notify and trigger external system

How to create custom “business events” in D365 Business Central to notify and trigger external system

I am thrilled to announce that I have been selected as a Microsoft MVP for the 12th year!!

I am thrilled to announce that I have been selected as a Microsoft MVP for the 12th year!!

Company creation failed with error in the Cloud Migration Tool – Business Central 22

 

Problem: We encountered the following error while running the Cloud Migration tool on the BC22 version.

We got the below details from the “Copy details” of the above screenshot.

 

If requesting support, please provide the following details to help troubleshooting:

Company creation failed with error Sorry, the current permissions prevented the action. (TableData Company Insert: Base Application). Please fix this and re-run the Cloud Migration Setup wizard.

Internal session ID: 
94e97f8f-95ae-46a4-a7b6-98c79e7a7dc3

Application Insights session ID: 
1379aeac-c297-4b34-a0a5-1ae811dd898c

Client activity id: 
10d32b54-bd85-464c-a6df-355bc967b607

Time stamp on error: 
2023-05-23T10:32:24.1598995Z

AL call stack: 
"Hybrid Cloud Management"(CodeUnit 4001).VerifyCanStartReplication line 11 - Intelligent Cloud Base by Microsoft
"Cloud Migration Management"(Page 40063)."RunReplicationNow - OnAction"(Trigger) line 4 - Intelligent Cloud Base by Microsoft

 

The User has SUPER permission set assigned.

Solution: Please check if the BC license is assigned to the user from M365.

The above error was resolved after assigning a BC license to the user from M365 (Office).

 

How to move Notes, RecordLinks while using #msdyn365bc Copy Documents