Introduction In this blog we will learn about the basic setups required for the Advanced Warehouse Management process. These setups may vary depending on the business scenarios. For Work classes and Work Templates to work in an Advance warehouse scenario, there are some prerequisites that we need to do first. The following are the setups that we need to configure:  Work classes and Work Templates plays a significant role in advanced warehouses. a Work classes and Work Templates are the set of rules to create the work for Purchase Order, Sales Order, Transfer Order etc.  For my current scenario, I will create a Work classes for a Sales Order, Purchase Order and Transfer Order.  – Enter Work Class ID and Description.  – Select work order type from the Drop-down menu.  – Here, I have created 4 work classes. We will use these work classes while making the work templates.  Work Templates:  Work templates will be used to create a work, when there is a related transactions like Purchase Order, Transfer Order, Sales Order etc.  By selecting this work, warehouse worker can perform the transaction on the mobile device.  – Click New.  – In the work Order type select Purchase Order.  – Enter Work template name  – Enter Work template Description  – Select the work type as “Pick” and “Put”  – Select previously created Work class ID as “PurchOrder”.  – Click New.  – In the work Order type select Sales Order.  – Enter Work template name  – Enter Work template Description  – Select the work type as “Pick” and “Put”  – Select previously created Work class ID as “SalesOrder”.  Now, Work classes and Work Templates are ready to use in Advance Warehouse process.  That’s it for this blog!!  How to use these Work classes and Work Templates in actual transactions will be discussed going forward in the blog series.  We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction In today’s busy work environment, having a smooth approval process is important for keeping things running efficiently. Dynamics 365 Business Central makes it easy to set up workflows that help manage approvals effectively. One great feature is the option to allow approval from “one of” several chosen approvers. This was one of our clients’ requirements to avoid delays and allows different team members to take part in the approval process. By letting any of the designated approvers approve requests, your organization can work faster and better together. In this guide, we’ll show you how to create a simple approval workflow in Dynamics 365 Business Central that requires just one approver from a group, making your approval process quicker and more efficient. Scenario: The purchase order has two approvers but if any one of them approves the approval workflow will be fulfilled. Hence, if one approver approves, all open approval entries will be closed. 1. Workflow user group As shown below the workflow user group, sequence no. 1 has been assigned to both the users. 2. Open the workflow for which this user group needs to be assigned. 3. Add the Workflow User Group to the Workflow – Open the response “add record restriction” – Add the workflow user group as the approver type and select the workflow user group created earlier. 4. Modify the events and conditions – Remove the “on condition to always” – Remove the third step 5. Additional response To close open approval entries after receiving a single approval, you must edit the second step and add the response, “Approve the approval request for the record.” – Click on the response of 2nd line ” remove record restriction” – Add response, ” “Approve the approval request for the record.” Conclusion In conclusion, setting up an approval workflow with flexible approvers in Dynamics 365 Business Central can significantly enhance the organization’s efficiency and responsiveness. By allowing any designated approver to handle requests, one can streamline the approval process and reduce potential delays. This approach not only fosters collaboration among team members but also ensures that important decisions are made quickly. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction In today’s fast-paced business environment, ensuring timely and accurate communication with your customers is critical. One of the most frequent interactions businesses have with customers is providing them with account statements. Microsoft Dynamics 365 Business Central simplifies this process, allowing users to send Customer Statements directly via email, streamlining communication and helping businesses maintain positive relationships with their clients. Steps to achieve the goal: 1. Log into Business Central Start by logging into your Business Central account. Ensure you have the necessary permissions to access customer information and send reports. 2. Access the Customer List Once logged in: 3. Select the Document Layout before you send an email to customers. 4. Setup Email Account (Optional if already configured) 4. Open the Statement Report Within the Customer Card: 5. Set Up the Statement Parameters Before generating the customer statement: 6. Send the Statement via Email Once the statement is ready: 8. Review and Send Once you’ve reviewed everything: Conclusion Sending customer statements via email in Business Central is a straightforward process that enhances customer communication while saving time. With just a few clicks, you can generate, customize, and send statements to your clients, ensuring that they stay informed about their account status. This efficient process helps you maintain accurate financial records, avoid payment delays, and ultimately, improve your cash flow. By leveraging Business Central’s customer statement feature, you can optimize your accounting workflows and focus more on growing your business. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction Encountering errors while working with Sales Orders in Dynamics 365 Finance and Operations (D365FO) can disrupt your workflow, especially in development environments. One common issue involves posting the packing slip due to an expired SSL certificate in cloud-hosted environments. SSL certificates in D365FO cloud-hosted setups are valid for one year, after which they need to be renewed for continued security and functionality I faced this issue while trying to post the packing slip for a Sales Order.  I faced this issue on Dev Environment. To resolve this issue, follow the below process: To maintain security, these certificates must be renewed through rotation. Credential rotation is a critical aspect of enterprise-level cybersecurity, and this process can be managed via LCS. To resolve this log into the LCS environment. – Select the Implementation Project and then click on Full details option. – Click on the Maintain drop down button and then select the Rotate Secrets. – After that click on Rotate SSL Secrets Certificates option. It will look like this. This process make take a few minutes to complete. This will resolve the issue. After completion you can see that the status will be changed to Deployed. Then the next and final step is to click on Apply updates option this will apply all the changes and updates. Conclusion Rotating SSL certificates in Dynamics 365 Finance and Operations is essential to maintain security and functionality in cloud-hosted environments. By following these steps in LCS, you can ensure that your environment remains secure and that tasks like posting packing slips proceed smoothly. Regularly checking and updating your SSL certificates will help prevent future disruptions and keep your operations running efficiently. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction In Purchase & trade agreements in D365 – Part 1 & 2 blog we have gone through overview of Purchase & trade agreements in D365 & how to setup different types of Purchase agreements in D365. In this blog will go through how to setup Trade agreement for Purchase price & how to setup different types of Trade agreement of line discount in D365. i.e. Fixed amount, percentage discount or for quantity range. Problem statement – In this scenario we need to setup different types of trade agreements for vendor. Solution steps – 1 – Will setup trade agreement for purchase price 1.1 Create Trade agreement journal names – Go to Procurement & Sourcing -> Setup -> Prices & discounts -> Trade agreement journal names 1.2 New -> Name -> Pur Price -> Description -> Purchase price Trade agreement -> Relation -> Price (purch.) -> Save. 1.3 Enable parameters – Go to Procurement & sourcing -> Setup -> Prices & discounts -> Activate price/discount 1.4 Enable all parameters for Price. Item parameter Yes for Vendor means It is to enable price for specific vendor for specific Item. Item parameter Yes for Vendor group means if price is same for item for group of suppliers (based on vendor group) then need to enable this parameter. Item parameter Yes for All vendors means if item has same prices for all suppliers then need to enable this parameter. 1.5 Create trade agreement journal. Go to Procurement & Sourcing -> Prices & discounts -> Trade agreement journals 1.6 Create new journal – Name -> Pur price (Created in step 1.2) -> click on Lines to add details 1.7 Enter line details.  Party code type -> Table -> Account selection -> VEN-000001 -> Product code type -> Table -> Item relation -> P-000009 -> Unit -> Pcs -> Amount in currency -> 3000 -> Save. 1.8 Validate -> Validate all lines 1.9 Post. 1.10 Then create new purchase order with respective vendor (In this case VEN-000001) for respective item (In this case P-000009). Purchase price will be reflected as per set in Trade agreement. 2 – Will setup trade agreement for Line discount for Fixed amount 2.1 Create Trade agreement journal names – Go to Procurement & Sourcing -> Setup -> Prices & discounts -> Trade agreement journal names 2.2 New -> Name -> Pur Disc -> Description -> Purchase discount -> Relation -> Line disc. (purch.) -> Save. 2.3 Enable parameters – Go to Procurement & sourcing -> Setup -> Prices & discounts -> Activate price/discount Enable all parameters for Price. Item parameter Yes for Vendor means It is to enable price for specific vendor for specific Item. Item parameter Yes for Vendor group means if price is same for item for group of suppliers (based on vendor group) then need to enable this parameter. Item parameter Yes for All vendors means if item has same prices for all suppliers, then need to enable this parameter. 2.4 Create trade agreement journal. Go to Procurement & Sourcing -> Prices & discounts -> Trade agreement journals Create new journal – Name -> Pur Disc (Created in step 2.2) -> click on Lines to add details 2.5 Enter line details.  Party code type -> Table -> Account selection -> VEN-000001 -> Product code type -> Table -> Item relation -> P-000009 -> Unit -> Pcs -> Amount in currency -> 100 -> Save. 2.6 Then validate & post the journal. 2.7 Then create new purchase order with respective vendor (In this case VEN-000001) for respective item (In this case P-000009) discount will be reflected as defined in Trade agreement. 3 – Will setup trade agreement for Line discount for discount % 3.1 As we have created already journal name & enabled parameters in solution 2, we can directly create journal. Create trade agreement journal. Go to Procurement & Sourcing -> Prices & discounts -> Trade agreement journals Create new journal – Name -> Pur Disc (Created in step 2.2) -> click on Lines to add details 3.2 Enter line details.  Party code type -> Table -> Account selection -> VEN-000001 -> Product code type -> Table -> Item relation -> P-000010 -> Unit -> Pcs -> Discount percentage 1 -> 10 -> Save. Then validate & post. 3.3 Then create new purchase order with respective vendor (In this case VEN-000001) for respective item (In this case P-000010) discount % will be reflected as defined in Trade agreement. 3.4 There is one more field available at Trade journal Discount percentage 2. Define Party code type -> Table -> Account selection -> VEN-000001 -> Product code type -> Table -> Item relation -> P-000011 -> Unit -> Pcs -> Discount percentage 1 -> 10 -> Discount percentage 2 -> 5 -> Save. Then validate & post. If both Discount percentage 1 & 2 is defined, then on Purchase value 1st discount in field 1 is applied & then on that value % of field 2 is applied. i.e. if amount 100 & disc 1 -10 & disc 2 – 5 then final % will be 100*.1=90*.05=85.5 so total discount will be 14.5%) 3.5 Then create new purchase order with respective vendor (In this case VEN-000001) for respective item (In this case P-000011) discount will be reflected as defined in Trade agreement. In this blog we completed how to setup Trade agreement for Purchase price & line discount fixed amount & discount percentage. In next blog (Part 4) will cover setup of trade agreement line discount for quantity range & next flag. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction How effectively are you tracking your company’s environmental impact? As sustainability becomes a growing priority, businesses need the right tools to monitor and manage their emissions. Dynamics 365 Business Central offers powerful features like the Chart of Sustainability Accounts (CoSA) and the Sustainability Ledger to help organizations streamline their sustainability efforts. In this guide, we’ll take a deep dive into how you can leverage these tools to enhance your environmental performance. What is the Chart of Sustainability Accounts (CoSA)? The Chart of Sustainability Accounts (CoSA) in Dynamics 365 Business Central is a specialized framework designed to manage emissions data, similar to a traditional chart of accounts but tailored for sustainability metrics. Key Features: Question: Have you already identified the key areas of your business that contribute to emissions? Think about where CoSA can help you focus on reducing your environmental impact. Managing Sustainability Accounts – Adding and Modifying Accounts Tip: Be cautious when deleting accounts. If they have existing ledger entries, you’ll need to resolve those before deletion to maintain data integrity. Interactive Element: Understanding Account Categories – Purpose and Setup Pro Tip: If your organization needs specific calculations, you can create custom formulas. This ensures that emissions are tracked accurately, even for complex or unique activities. Calculation Foundations The system uses different methods to calculate emissions based on the emission type and category. Here are some examples: Interactive Question: Have you considered which scope of emissions contributes the most to your environmental footprint? Scope 1, 2, or 3? Account Subcategories – Purpose and Setup Did You Know?: You can also set up renewable energy-related subcategories. By marking the Renewable Energy field, you can easily track the impact of renewable energy use in your operations. Interactive Element: Have you considered using renewable energy in your business? Start tracking it separately in CoSA to measure its impact on your emissions. Sustainability Ledger Entries – Purpose and Management Correcting Errors Once data is posted, it cannot be deleted. To correct errors, simply post a reverse transaction with the same details but a negative amount. Interactive Tip: Worried about data entry mistakes? Start with a test entry in the ledger to familiarize yourself with the system before posting live data. Conclusion The Chart of Sustainability Accounts and Sustainability Ledger in Dynamics 365 Business Central are invaluable tools for businesses aiming to reduce their environmental impact. By properly configuring CoSA, setting up categories and subcategories, and using the sustainability ledger, you can gain deeper insights into your emissions and improve your sustainability practices. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Managing financial transactions accurately and efficiently is crucial for any growing business. The process of ledger settlements can be time-consuming and prone to errors when done manually. To address this, Microsoft Dynamics 365 Finance version 10.0.31 introduces the ability to automate ledger settlements, helping businesses streamline their financial processes. In this article, we’ll walk you through the steps needed to enable and optimize automatic ledger settlements in Dynamics 365, so your organization can save time, reduce errors, and improve financial reporting. Automating ledger settlements is a significant improvement over the manual process. The automated process works by comparing debit and credit transactions in your general ledger. It automatically matches transactions with identical accounting currency amounts, simplifying reconciliation efforts. However, it’s important to note that this feature does not support partial matching of transactions. Before enabling the Automate Ledger Settlements feature, it’s crucial to first activate the Awareness feature between Ledger Settlement and Year-end Close. This step ensures the process runs smoothly without impacting your year-end financial closing. Steps to Enable Automatic Ledger Settlements Step 1: Identify Relevant Primary Accounts Step 2: Create a Rule for Process Automation Step 3: Set up Criteria for Automation Step 4: Manage the Created Rule Once the rule has been created, you can view or modify it at any time. This flexibility allows you to adapt the automation process to changing business needs. Step 5: Verify the Automation Batch Job Ensure that the automation batch job is running correctly. Go to System Administration > Inquiries > Batch Jobs to check the execution status. Step 6: View Scheduled Executions and Results You can monitor the status of your scheduled automations and the results of settled transactions for full visibility into your financial processes. Step 7: Access Settled Transactions To view finalized ledger settlements, navigate to General Ledger > Periodic Tasks > Ledger Settlements. Conclusion By automating the ledger settlement process in Dynamics 365 Finance, businesses can reduce manual effort, minimize errors, and optimize financial workflows. It’s essential to follow the steps outlined above to ensure smooth implementation and operation. By automating your ledger settlements, your organization can save time and improve financial reporting accuracy. Take the Next Step If your organization is looking to optimize financial workflows, start by automating your ledger settlements today. For more detailed assistance or to explore additional financial automation features, feel free to contact us.

Introduction Are you looking to enhance your business’s sustainability efforts? Dynamics 365 Business Central’s Sustainability Management feature helps businesses monitor, manage, and report their environmental impact, with a focus on greenhouse gas (GHG) emissions. With this tool, you can track your emissions across various scopes to align with your company’s sustainability goals. But how can you ensure this tool is properly configured to maximize its benefits for your organization? Key Features and Capabilities 1. Emission Tracking Imagine being able to track emissions across multiple dimensions. Here’s how the tool categorizes them: Tip: Start by listing all the potential sources of emissions in your business. Can you think of ways to reduce emissions in Scope 1 or 2 right now? 2. Setup and Configuration Setting up this feature correctly is key to getting meaningful data. Pro Tip: If you’re unsure where to begin with emission factors, consider consulting with a sustainability expert to ensure you’re using accurate numbers. 3. Data Management Question: Which areas of your business could benefit most from detailed emission tracking—your supply chain, your operations, or perhaps both? 4. Reporting and Insights Call to Action: Ready to see how these reports can help streamline your sustainability goals? Schedule a demo today to explore the full reporting capabilities! Benefits Still wondering if this feature is right for your business? Here’s what you stand to gain: Example: One of our clients reduced their Scope 2 emissions by 15% after better understanding their energy consumption patterns using Business Central’s data management features. Step-by-Step Setup Guide To configure the Sustainability module in Dynamics 365 Business Central, follow these steps carefully. Don’t worry if you’re not familiar with all the terms—we’ll guide you through each section: 1. General Fast-Tab Configuration Tip: Choosing the right level of precision can make a big difference in how your data is interpreted. 2. Calculations Fast-Tab Configuration Pro Tip: If your emissions are mostly related to transportation, focus on fine-tuning the distance and fuel data. 3. Reporting Fast-Tab Configuration (Note: This section is for future reporting capabilities) Did you know? Although this feature isn’t available in version 24.0, it will be in future updates. Stay ahead by configuring the settings now! Conclusion The Sustainability Management feature in Dynamics 365 Business Central provides critical tools for managing your environmental footprint. By configuring units of measure, decimal places, and reporting parameters, you can tailor the system to meet your business’s sustainability goals. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction Seamless integration between systems is essential for efficient operations and data accuracy. One of the common integration challenges is syncing data between Customer Relationship Management (CRM) systems and Finance and Operations (FNO) systems. Traditionally, dual write has been a solution for this integration, but it comes with limitations. In this blog, we’ll explore a real-life business use case where we replace dual write with Azure Logic Apps to enable real-time data synchronization between CRM and FNO systems. Understanding Dual-Write Dual write is a framework provided by Microsoft that ensures data consistency between Dynamics 365 Finance and Operations (FNO) and Dynamics 365 Customer Engagement (CRM) applications. It facilitates real-time and bi-directional data synchronization, maintaining records of table and field mappings between FNO and CRM. This ensures that any change made in one system is reflected in the other, providing a unified experience across the enterprise. However, dual-write has its limitations, such as complex setup, limited customization options, and potential performance issues in high-transaction environments. These limitations prompt businesses to seek more flexible and scalable integration solutions. The Business Use Case: Replacing Dual-Write with Azure Logic Apps Scenario: A manufacturing company uses Dynamics 365 CRM to manage customer interactions and Dynamics 365 FNO to handle finance and operations. The company relies on dual write to keep customer data synchronized between the two systems. However, they face issues with the dual-write setup, including occasional synchronization lags and difficulties in customizing data mappings. To overcome these challenges, they decide to implement Azure Logic Apps for real-time data synchronization between CRM and FNO. Objective: Create a Logic App that enables real-time data synchronization between CRM and FNO, replacing the existing dual-write setup. This Logic App will ensure that any changes in customer data in CRM are immediately reflected in FNO and vice versa, without the complexities and limitations of dual write. Steps to Implement the Solution Benefits of Using Azure Logic Apps Conclusion By replacing dual write with Azure Logic Apps, the manufacturing company can achieve a more reliable and customizable integration between their CRM and FNO systems. This solution not only enhances data consistency and real-time synchronization but also provides the flexibility to adapt to future business requirements. Azure Logic Apps empower businesses to streamline their operations, improve data accuracy, and ultimately deliver better customer experiences. In our next blog, we will explore in detail how this business use case can be fully implemented using Azure Logic Apps. Stay tuned for a step-by-step guide on setting up the Logic App, configuring connectors, and ensuring seamless real-time data synchronization between CRM and FNO. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com

Introduction In Purchase & trade agreements in D365 – Part 1 blog we have gone through overview of Purchase & trade agreements in D365 & how to setup different types of Purchase agreements in D365. In this blog will go through how to setup purchase agreement of type Product category value commitment & Value commitment. To give brief overview of Purchase & trade agreements in D365, for those who have not gone through part 1 of this blog. In D365 we can create Purchase agreements for blanket orders to buy certain fixed quantity of item from specific vendor within specified time. & Trade agreement can be used to create discounts generally for short period for specific vendor or vendor group. In D365 there are different types of Purchase agreement & trade agreements. Below are different types of Purchase agreements based on commitment in D365 – Product category value commitment is setup when there is commitment to buy fixed amount of specific category of goods from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy Travel luggage bags category SKUs from vendor A worth 10million over next 1 year then vendor will offer 20% discount for same. Value commitment when there is commitment to buy fixed amount from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy from vendor A worth 15million over next 1 year then vendor will offer 20% discount for same. Below are different types of Trade agreements based on relation in D365 – Problem statement – In this scenario we need to setup purchase agreement of type Product category value commitment & Value commitment for vendor. Solution steps – 1 – Will create purchase agreement for Product category value commitment 1.1 Go to Procurement & Sourcing -> Purchase agreements -> Purchase agreements 1.2 Click on New -> Vendor account -> Select respective vendor (In this case it is VEN-000002) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Product category value commitment -> Effective date -> Select respective date (In this case it is 1 Aug 24) -> Expiration date -> Select respective date (In this case it is 1 Aug 25) -> Ok 1.3 Fill the respective details of Item/Category name – Spinner, Net amount – 100000, Discount percent – 15 & Max enforced – Yes. Max enforced Yes means quantity consumed against purchase agreement is tracked. If purchase quantity exceeds quantity mentioned in agreement, then message will be displayed & link of Purchase agreement is removed from purchase order. & confirm purchase agreement. 1.4 Then create new Purchase order, select Purchase agreement to link 1.5 Add any Item with category mentioned in purchase agreement, in this case it is “Spinner” & required quantity in purchase order, discount will be automatically taken from purchase agreement. 1.6 We can check which agreement is linked, click on Update line -> Purchase agreement -> Attached. 1.7 Similarly, In Purchase agreement also same is reflected. 2 – Will create purchase agreement for Value commitment 2.1 Go to Procurement & Sourcing -> Purchase agreements -> Purchase agreements -> Click on New -> Vendor account ->  Select respective vendor (In this case it is VEN-000005) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Value commitment -> Effective date ->  Select respective date (In this case it is 1 Aug 24) -> Expiration date ->  Select respective date (In this case it is 1 Aug 25) -> Ok 2.2 Fill the respective details of Item/Category name – can select highest category in this case it is Bags, Net amount – 500000, Discount percent – 20 & Max enforced – Yes. Max enforced Yes means quantity consumed against purchase agreement is tracked. If purchase quantity exceeds quantity mentioned in agreement, then message will be displayed & link of Purchase agreement is removed from purchase order. & confirm purchase agreement. 2.3Then create new Purchase order, select Purchase agreement to link 2.4 Add any Item with category mentioned in purchase agreement in this case it is “Bag” & required quantity in purchase order, discount will be automatically taken from purchase agreement. 2.5 We can check which agreement is linked, click on Update line -> Purchase agreement -> Attached. In this blog we completed purchase agreement types. In next blog (Part 3) will cover setup of trade agreement. We hope you found this article useful, and if you would like to discuss anything, you can reach out to us at transform@cloudfronts.com