In today’s fast-paced business world, integrating your ERP system (like Business Central) with other external systems is crucial for streamlining processes and ensuring data consistency. However, if you’re new to API integrations or struggling with how to send data from Business Central to another system, don’t worry! In this post, I am going to walk you through the process of sending data from Business Central to an external system using APIs. By the end of this guide, you’ll have a clear understanding of how to perform integrations smoothly, without the complexity. Steps to Achieve Goal: You can easily send data from Business Central to an external system by calling the link set in General Ledger Setup. Below is the logic for sending data via an API. You can encapsulate this logic inside a Codeunit, and call it as needed based on your synchronization requirements: Real-Time Data Sync: If you want the data to be synced in real-time (for example, as soon as new data is entered into Business Central), you can call the procedure within the OnAfterInsert() trigger. This ensures that every time a new record is created, it automatically triggers the procedure to send the data. trigger OnAfterInsert() begin     SendPostRequest(Rec); end; Batch Data Sync: If you prefer to sync the data at the end of a batch process (for example, at the end of the day), you can loop through the records using FindSet() and then call the procedure inside the loop. This will send data in bulk at a scheduled time rather than in real-time. procedure SyncDataInBatch() var     Rec_SO: Record “Sales Header”; begin    Rec_SO.setrange(CreatedAt,today()); // Apply any filter as per your need.     if Rec_SO.FindSet() then         repeat             SendPostRequest(Rec_SO);         until Rec_SO.Next() = 0; end; // Below is the logic for posting data from BC to Third Party Applications via API   procedure SendPostRequest(var Rec_SO: Record “Sales Header”)     var         HttpClient: HttpClient;         HttpContent: HttpContent;         HttpResponseMessage: HttpResponseMessage;         HttpRequestMessage: HttpRequestMessage;         JsonObject: JsonObject;         JsonText: Text;         Rec_GLE: Record “General Ledger Setup”;         contentHeaders: HttpHeaders;         OutPutString: Text;     begin           Rec_GLE.Get();         Rec_GLE.TestField(“API Link”); // where the other system API link has been stored and we are using via AL         HttpRequestMessage.SetRequestUri(Rec_GLE.”API Link”);         HttpRequestMessage.Method := ‘POST’;         JsonObject.Add(‘system_id’, Rec_SO.SystemId); // Passing Sales Header System ID(GUID)         JsonObject.Add(‘document_number’, Rec_SO.”No.”); // Passing Sales Header No         JsonObject.Add(‘type’, ‘ReleasedSalesInvoice’); // Passing Sales Header type         JsonObject.WriteTo(JsonText);         HttpContent.WriteFrom(JsonText);           HttpContent.GetHeaders(contentHeaders);         contentHeaders.Add(‘charset’, ‘UTF-8’);         contentHeaders.Remove(‘Content-Type’);         contentHeaders.Add(‘Content-Type’, ‘application/json; charset=utf-8’);           HttpRequestMessage.Content(HttpContent);         if HttpClient.Send(HttpRequestMessage, HttpResponseMessage) then             if HttpResponseMessage.IsSuccessStatusCode then begin                 HttpResponseMessage.Content.ReadAs(OutPutString);                 Message(‘%1’, OutPutString);             end             else                 Error(‘Error %1’, HttpResponseMessage.ReasonPhrase);     end; Conclusion: To conclude, sending data between Business Central and other systems is not as complicated as it might seem. By following the steps outlined above, you’ll be able to create smooth, efficient integrations that will save time, reduce errors, and improve your business processes. Happy Coding! We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

In the world of corporate reporting, presentation matters just as much as data. The more personalized and professional your reports look, the more impactful they become. If you’re using Dynamics 365 Finance and Operations (F&O), chances are you rely on SSRS (SQL Server Reporting Services) reports to generate vital business insights. But have you ever wondered how to make those reports more aligned with your company’s branding? Are you struggling with adding your company logo to SSRS reports in F&O? I am going to show you how to easily embed your corporate logo into your SSRS reports within Dynamics 365 F&O, transforming your data into visually appealing reports that reflect your brand identity. Whether you’re preparing financial statements, customer invoices, or custom reports, adding a logo enhances the look and feel, ensuring that your reports maintain a consistent and professional corporate image. Steps to Achieve the goal Before embedding your logo into the SSRS report, ensure that the image file (usually in PNG, JPG, or GIF format) is prepared and accessible. You need to upload the logo to a location within the F&O environment where your SSRS report can access it. Follow these steps: To conclude, adding your company logo to your SSRS reports in Dynamics 365 Finance & Operations is a powerful way to enhance your brand’s presence across all reports. You can instantly elevate the look and feel of your documents. Happy Coding! We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

By the end of this guide, you will be able to generate, edit, and implement XLIFF files in Microsoft Dynamics 365 Business Central to support multiple languages seamlessly. This will enable your application to display translated content for UI labels, reports, and messages, ensuring a smooth experience for users across different regions. Why does this matter? Using XLIFF files, businesses can easily localize Business Central applications without modifying source code, making multilingual support efficient and scalable. By leveraging tools like NAB AL Tools, translations can be managed effortlessly, enhancing global usability. Generating an XLIFF File To illustrate the XLIFF process, let’s go through an example where we add a custom field named “Custom_Field” on the Customer Card page. Step 1: Creating a Custom Field First, we create a new field, Custom_Field, on the Customer Card page using AL code: Step 2: Enabling Translation File Feature In the app.json file, ensure that the TranslationFile feature is enabled: Step 3: Building the Project Now, build the extension using the shortcut CTRL + Shift + B. This will generate an .xlf file automatically in the translation folder. By default, the file is generated in English (en-US). Using NAB Extension for Translation To simplify translation tasks, you can install the NAB AL Tools extension from the Visual Studio Code marketplace. This extension helps in managing translation files efficiently by allowing automated translation suggestions and quick file updates. Steps to Use NAB AL Tools: A) Install NAB AL Tools. B) Press CTRL + Shift + P and select NAB: Create translation XLF for new language. C) Enter the language code (e.g., fr-FR for French – France). D) Choose Yes when prompted to match translations from BaseApp. E) A new fr-FR.xlf file will be generated. Translating the XLIFF File To translate the XLIFF file into another language (e.g., French), follow these steps: Example: Translating Report Labels In Business Central RDLC reports, hardcoded text values can also be translated using labels. Instead of writing static text, define labels within the AL code: Using FieldCaption ensures that report labels dynamically adapt to the selected language, improving localization without manual modifications. When switching languages, the label automatically retrieves the corresponding translation from the XLIFF file. Modifying Standard Fields Standard field names in Business Central can also be modified using the BaseApplication.g.xlf file. You can find this file in public repositories, such as: BaseApplication.g.xlf Modifying this file allows changes to default field captions and system messages in multiple languages. Insert value in different languages via AL In Microsoft Dynamics 365 Business Central, AL enables efficient multilingual data handling. The image above illustrates a Customer Card where the “Nom” (Name) field contains the value “testing.” The AL code extends the Customer table, adding a custom field and an onInsert trigger to validate the Name field with “testing.” This ensures data consistency across different language settings. By leveraging AL, developers can automate multilingual field values, enhancing Business Central’s global usability. To conclude, managing translations in Business Central using XLIFF files enables businesses to support multiple languages efficiently. By generating XLIFF files, modifying them for translation, and leveraging tools like NAB AL Tools, businesses can ensure accurate and seamless localization. For further refinements, modifying report labels and system fields enhances multilingual support, improving the user experience across global deployments. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

In today’s globalised world, firms frequently operate in numerous areas and languages. To efficiently manage worldwide operations, software with multilingual capabilities is required. Microsoft Dynamics 365 Business Central (BC) includes a powerful translation system that enables enterprises to customise language choices, thereby increasing user experience and operational efficiencies. This article looks at how translations function in Business Central and how they may be used to support global business operations. Why Are Translations Important in Business Central? Businesses that expand into new areas face a variety of languages, currencies, and regulatory regimes. Ensuring that employees can interact with Business Central in their native language improves the software’s usability and productivity. Business Central allows users to configure numerous languages across various modules, allowing workers to work smoothly in their favourite language. It also allows translations for custom fields, reports, and data entry, assuring consistency and correctness in both internal and external interactions. How Translation Works in Business Central Business Central supports several languages, including English, French, German, and Spanish. Here’s an outline on how to activate and use translations successfully. 1. Configuring Language Settings The first step in enabling multilingual support is to configure the Language Settings in Business Central. Users can choose their favourite language or use the organization’s default language settings. This guarantees that when a user logs in, the interface, menus, and forms appear in their preferred language. To configure a language in Business Central: 2. Standard Text Translations Business Central provides built-in translations for standard interface elements and commonly used terms such as “Sales Orders,” “Invoices,” and “Purchase Orders.” These translations are included in the base application by Microsoft. For example, changing the language from English to French automatically updates the captions. However, some standard texts may not be translated by default. To install additional language support: Once installed, the system updates with the new language settings, ensuring a localized user experience. 3. Translating Custom Fields Many businesses customize Business Central by adding custom fields, tables, and industry-specific terminology. While these enhancements improve operational efficiency, they may not be automatically translated in the base system. To resolve this, Business Central provides the CaptionML property, which allows developers to define multilingual captions for custom elements. Example: English: Displays field names and labels in English. French: The same fields are shown with French translations. By implementing the CaptionML property, businesses ensure a seamless multilingual experience even for customized elements. To conclude, Microsoft Dynamics 365 Business Central makes it simple for multinational companies to handle multilingual customers. Companies can improve usability and efficiency across regions by changing language settings, adding extra translations, and ensuring that custom fields are translated using CaptionML. Embracing Business Central’s translation skills enables firms to operate efficiently in a global market while providing a consistent and localized experience to all users. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

Managing your organization’s data effectively is a critical task for ensuring business continuity. Dynamics 365 Business Central simplifies this process by offering built-in backup and restore features via the Business Central Admin Center. In this blog, we’ll explore how you can utilize these features to safeguard your environment and handle potential mishaps. Overview of Backups in Dynamics 365 Business Central Business Central automatically manages backups for your production and sandbox environments. These backups are stored securely for a limited period, allowing administrators to restore environments when needed. The retention period and capabilities for restoring backups are influenced by the environment type (production or sandbox). Key Features of the Backup System Restoring an Environment Restoring an environment is a straightforward process, ensuring minimal downtime. Follow these steps to restore an environment using the Admin Center: Step 1: Access the Admin Center Log in to the Business Central Admin Center using your administrator account. Step 2: Select the Environment Navigate to the Environments page and select the environment you wish to restore. Step 3: Initiate the Restore Process Click on the Restore button and choose a backup point from the available restore options. Step 4: Configure Restore Options Step 5: Confirm the Action Review the details and confirm the restore. The system will notify you once the process is complete. To encapsulate, the backup and restore functionalities in Dynamics 365 Business Central offer a reliable safety net for your organization’s data. By leveraging the Admin Center, administrators can easily safeguard business continuity and minimize risks associated with data loss or corruption. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

Azure Function Apps are a powerful tool for creating serverless applications, but losing the underlying code can be a stressful experience. Whether due to a missing backup, accidental deletion, or unclear deployment pipelines, the need to recover code becomes critical. Thankfully, even without backups, there are ways to retrieve and reconstruct your Azure Function App code using the right tools and techniques. In this blog, we’ll guide you through a step-by-step process to recover your code, explore the use of decompilation tools, and share preventive tips to help you avoid similar challenges in the future. Step 1: Understand Your Function App Configuration Step 2: Retrieve the DLL File To recover your code, you need access to the compiled assembly file (DLL).From Kudu (Advanced Tools), navigate to the site/wwwroot/bin directory where the YourFunctionApp.dll file resides and download it. Step 3: Decompile the DLL File Once you have the DLL file, use a .NET decompiler to extract the source code by opening .dll file using a .Net decompiler and running the decompiler script. The decompiler I have used here is dotPeek which is a free .Net decompiler. To Conclude, recovering a Function App without backups might seem daunting, but by understanding its configuration, retrieving the compiled DLL, and using decomplication tools, you can successfully reconstruct your code. To prevent such situations in the future you can enable Source Control to Integrate your Function App with GitHub or Azure DevOps or set backups. We hope you found this blog post helpful! If you have any questions or want to discuss further, please contact us at transform@cloudfronts.com. Please refer to our customer success story Customer Success Story – BUCHI | CloudFronts to know more about how we used the function app and other AIS to deliver seamless integration. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

Debugging Power Pages (formerly Power Apps Portals) can be tricky, especially when errors don’t show up clearly. One underrated but powerful method is using the browser’s “View Page Source” feature to uncover hidden issues. In this blog, we’ll explore how to use HTML source code inspection to diagnose problems in Power Pages, including: Use Case Imagine you’ve built a customer portal with dynamic content using Liquid templates, but: Manually checking each element is time-consuming. Instead, use these two pro techniques to pinpoint issues fast. Method 1: Debugging Using “View Page Source” Step 1: Access the Page Source Step 2: Check for Liquid Rendering Errors Power Pages uses Liquid templates to render dynamic content. If a Liquid snippet fails, it may appear as: Example: Debugging a Broken FetchXML Query Consider this Liquid Code in your Portal page but the data does not render In the page source, look for: This tells you the issue is table permissions, not the query itself. Method 2: Debugging Using Hidden <div> Tags If you need real-time frontend debugging, inject hidden <div> tags to display variables. Add a Hidden Debug <div> Place this in your Liquid template: Inspect with Browser DevTools <div> Example: Debugging a Missing Username If {{ user.fullname }} appears blank: Results Let’s test it – In this case, my fetchXML result is not rendering, so I wanted to verify if I have the necessary roles as well as the user information. By using your browser’s “View Page Source” feature and strategically placed hidden debug <div> tags, you can quickly uncover hidden Liquid errors, verify data rendering, and troubleshoot Power Pages issues more efficiently. These simple yet powerful techniques eliminate guesswork, help identify permission problems, and let you validate variables without disrupting the user experience – ultimately saving you valuable development time while maintaining cleaner, more reliable portals. (Pro Tip: Combine these methods with browser DevTools for even deeper debugging capabilities!) We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

Power BI is a great tool for turning data into clear, interactive reports and the best part?  It works smoothly with Business Central, right out of the box.  You just need to set it up, and you can start viewing powerful reports right inside within Business Central dashboard.  Microsoft provides several ready-made reports, grouped into different apps, so you can pick and install only what you need.  Once set up, these reports help you track key business insights without switching between systems.  In this blog, we’ll walk you through how to set up and use Power BI reports in Business Central to make smarter decisions. References Introduction to Business Central and Power BI Install Power BI apps for Business Central Configuration Open your Business Central and search for “Assisted Setup”. Click on “Connect to Power BI” Once the set up page opens, click on Next. Fiscal: A 12-month calendar that begins in any month and ends 12 months after. Standard: A 12-month calendar that begins on January 1 and ends on December 31. Weekly: A calendar that supports 445, 454, or 544 week groupings.The first and last day of the year might not correspond to a first and last day of a month, respectively. Specify the time zone. Specify the working days. Here, it asks for configuring individual apps for Power BI. You can skip this for now as we’ll be back at this later. In the next screen, specify the environment name and the company name. Now, we’ll install the “D365 Business Central – Sales” app in Power BI. Go to your Power BI dashboard and click on Apps.  Search for Business Central Open the relevant one and click on “Get it now” Then click on “Install” Wait for a few seconds till the installation is complete. Now, when you open the report for the first time, it’ll show the report with sample data. To view it with your own data, we need to connect the data to Business Central. Enter the company and environment name. Specify the authentication method to OAuth 2.0 and click on “Sign in and connect” After a few minutes, the refresh will be completed and you’ll see your data. Once this is done, search for “Power BI Connector Setup” In the relevant tab, Sales Report for this example, click on “Power BI Sales” field’s drill down. Select the app that you installed. Now go back to your Business Central dashboard and scroll down to the “Power BI” section. Click on the “Get Started with Power BI” and keep clicking on Next till the end of the setup. If there are any selected reports, you will see the relevant report. If not, you’ll see the following-  In either case, click on the drop-down next to Power BI or click on the “Select reports” Scroll down to find the appropriate report and click on “Enable” and then click on Ok. You will see your Power BI report on the dashboard. You can enable multiple reports and cycle through them by clicking on the “Next” and “Previous” buttons. You can also expand the report to see it as a full page within Business Central by clicking on the “Expand” page. You can further view it in Fullscreen as well. If you want to see multiple reports on the same page, we can create a custom role center and add multiple reports to them. For example, I’ve created a “Power BI dashboard” role center. In this way, we can have n number of reports on our dashboard. Source Code – BCApps-PowerBIDashboard Setting up Power BI in Business Central is a simple way to bring your data to life.  With just a few steps, you can connect your reports, see real-time insights, and make better business decisions all without leaving Business Central.  Whether you need sales trends, financial reports, or custom dashboards, Power BI makes it easy to track what matters most. If you need further assistance or have specific questions about your Business Central and Power BI Integration, feel free to reach out for personalized guidance. We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

In modern cloud-based applications, real-time monitoring is crucial for detecting performance bottlenecks, identifying failures, and maintaining application health. Azure Live Metrics is a powerful feature of Application Insights that allows developers and operations teams to monitor application telemetry with minimal latency. Unlike traditional logging and telemetry solutions that rely on post-processing, Live Metrics enables real-time diagnostics, reducing the time to identify and resolve issues. What is Azure Live Metrics? Azure Live Metrics is a real-time monitoring tool within Azure Application Insights. It provides instant visibility into application performance without the overhead of traditional logging. Key features include: Benefits of Azure Live Metrics 1. Instant Issue Detection With real-time telemetry, developers can detect failed requests, exceptions, and performance issues instantly rather than waiting for logs to be processed. 2. Optimized Performance Traditional logging solutions can slow down applications by writing large amounts of telemetry data. Live Metrics minimizes overhead by using adaptive sampling and streaming only essential data. 3. Customizable Dashboards Developers can filter and customize Live Metrics dashboards to track specific KPIs, making it easier to diagnose performance trends and anomalies. 4. No Data Persistence Overhead Unlike standard telemetry logging, Live Metrics does not require data to be persisted in storage, reducing storage costs and improving performance. How to Enable Azure Live Metrics To use Azure Live Metrics in your application, follow these steps: Step 1: Install Application Insights SDK For .NET applications, install the required NuGet package: For Java applications, include the Application Insights agent: Step 2: Enable Live Metrics Stream In your Application Insights resource, navigate to Live Metrics Stream and ensure it is enabled. Step 3: Configure Application Insights Modify your appsettings.json (for .NET) to include Application Insights: For Azure Functions, set the APPLICATIONINSIGHTS_CONNECTION_STRING in Application Settings. Step 4: Start Monitoring in Azure Portal Go to the Application Insights resource in the Azure Portal, navigate to Live Metrics, and start observing real-time telemetry from your application. Key Metrics to Monitor Best Practices for Using Live Metrics To conclude, Azure Live Metrics is an essential tool for real-time application monitoring, providing instant insights into application health, failures, and performance. By leveraging Live Metrics in Application Insights, developers can reduce troubleshooting time and improve system reliability. If you’re managing an Azure-based application, enabling Live Metrics can significantly enhance your monitoring capabilities. Ready to implement Live Metrics? Start monitoring your Azure application today and gain real-time visibility into its performance! We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.

Microsoft Dynamics 365 Finance & Supply Chain (D365 F&SC) is a powerful enterprise solution designed to optimize business operations. To enhance workflow management, Microsoft has introduced a new feature that allows organizations to set up a dedicated email ID for users to receive workflow-related notifications. This feature, available in the Feature Management area of D365 F&SC, helps streamline communication and ensures that important workflow notifications reach the right users efficiently. In this blog, we will cover:✔ How to enable this new feature.✔ How workflow notifications are managed.✔ Practical use cases, including an Accounts Payable example.✔ The key benefits of this enhancement. Enabling the Alternate Email Feature for Workflow Notifications To activate this feature, follow these steps: Outcome: Once enabled, all workflow-related emails will be sent to the email ID specified in the Alternate Email field. Managing Workflow Notifications with the Alternate Email Field Key Aspects of Workflow Email Management: Primary Email for Notifications: Fallback to Sender Email Field: Use Case: Accounts Payable Email Alias for Payment Advice Notifications Scenario:An organization uses ACH payments to pay vendors, and the Accounts Payable (AP) team wants to send payment advice notifications from a shared email alias rather than their personal email IDs. Solution Using the Alternate Email Feature: Set the Sender Email field to the Accounts Payable email alias (e.g., ap@company.com). Configure individual user accounts to use their personal email under the Alternate Email field. As a result, vendors will receive payment advice emails from the Accounts Payable alias instead of a user’s personal email. Benefit:This approach improves consistency in external communications and ensures that vendors recognize the payment notifications as coming from the official Accounts Payable department. Key Benefits of the Alternate Email Feature Simplified Workflow Management Increased Efficiency Better Team Collaboration Improved Vendor Communication To conclude, the Alternate Email ID for Workflow Notifications feature in D365 Finance & Supply Chain is a game-changer for businesses looking to enhance workflow management. By enabling this feature, organizations can streamline communication, improve collaboration, and reduce email clutter for users. With this new enhancement, users can efficiently track their workflows without the hassle of checking multiple email accounts—leading to greater productivity and better business operations. Need assistance implementing this feature? Let us know in the comments or reach out for expert guidance! We hope you found this blog useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfonts.com.