"Unveiling the Mystery: Forex Revaluation Entries Posted Outside End-of-FY in Business Central - What Could Be the Reasons?"

 Hello reader,

I encountered the above problem when i ran forex revaluation.

Certainly! Here are two key points to address the issue of invoices applied to post-FY payments/receipts in Business Central:

Issue: Invoices falling within the previous financial year were paid and applied to payments/receipts posted after the financial year ended, leading to discrepancies in financial reporting.

Solution: Un-applying the receipts and payments. By reversing the application process, we can remove the linkage between the invoices and the post-FY transactions, ensuring accurate financial records

Action Steps:

a. Identify the invoices that were applied to post-FY payments/receipts and determine the correct financial period they should be associated with.

b. Un-apply the affected receipts and payments associated with those invoices. This will detach them from the incorrect financial period.

c. Re-apply the receipts and payments to ensure they are correctly assigned to the appropriate financial year, maintaining accurate financial reporting.

By following these steps, we can resolve the issue of invoices applied to post-FY payments/receipts and ensure the integrity of your financial data in Business Central. If you require further assistance, don't hesitate to reach out for support.

Why the fields you added to the child extension in business central do not show in the parent extension using AL

Resolving Field Access Issues in Parent Extensions for Microsoft Dynamics 365 Business Central

Introduction: As a Business Central developer, it is not uncommon to encounter challenges when working with extensions, particularly when accessing fields in child extensions from parent extensions. In this article, we will address a common issue where newly added fields in a child extension are not accessible in the parent extension. We will provide a solution to ensure smooth integration and seamless access to these fields within the parent extension.

Solution:

1. Update the Child Extension Version: To begin, it is crucial to update the version of the child extension in the app.json file. For example, if the current version is 1.0.0.0, increment it to 1.0.0.1. This version update ensures that the latest changes are recognized and applied throughout the system.

2. Update Parent Extension Dependencies: Next, update the dependencies in all parent extensions to reflect the new version of the child extension. This step establishes the necessary connection between the parent and child extensions, allowing for proper integration and field access.

3. Compile, Package, and Publish the Child Extension: After updating the version and dependencies, proceed to compile, package, and publish the child extension. This step ensures that the extension's changes are properly bundled and deployed for use in the Business Central environment.

4. Download Symbols in Parent Extensions: To enable seamless communication between the parent and child extensions, it is essential to download symbols in the parent extensions that have a dependency on the child extension. Symbol downloading facilitates the recognition and utilization of the updated fields.

5. Package and Publish the Parent Extension: Finally, package and publish the parent extension, incorporating the changes made in the child extension. This process allows the parent extension to recognize and access the newly added fields successfully.

Conclusion:

By following these steps, you can resolve field access issues encountered when working with parent and child extensions in Microsoft Dynamics 365 Business Central. Remember to exercise caution and perform these operations on a test environment before applying them to a production environment. Maintaining a comprehensive backup of your database is also crucial to mitigate any potential risks associated with these modifications.

As a Business Central developer, it is essential to be equipped with the knowledge and expertise to address these types of challenges. By implementing this solution, you can ensure a smooth and efficient integration of extensions, enabling optimal functionality within the Business Central environment.

Good luck!!

How to substitute a default report with a custom report in Business Central on premise

 

Hello Reader,

If you are reading this then probably you have been checking a couple of resources to find a solution to the stated issue.

I had a similar challenge and after spending a couple of hours checking online resources, I found it very easy !

    

Follow these steps.

Create your custom report in a new extension. If you don't know how to create extensions follow this

After creating your Custom report in the extension, you will have to create a code unit with subscriber event to codeunit Report management.

Just publish and run your extension. You should have your reports substitution successful

Here is a sample 

codeunit 100 "GP Base Report Substittuion"

{

    trigger OnRun()

    begin

    end;

[EventSubscriber(ObjectType::Codeunit, Codeunit::ReportManagement,

'OnAfterSubstituteReport', '', false, false)]

    local procedure OnSubstituteReport(ReportId: Integer; var NewReportId: Integer)

    begin

//Reminder is the name of the default report object in Business Central

        if ReportId = Report::Reminder then

            NewReportId := Report::GPReminder;

//GPReminder is the name of the custom report you created to substitute the default

// report

    end;

}