Introduction Open Data Protocol (oData) is a web protocol for querying and updating data. It simplifies the data exchange between clients and servers, allowing for easy integration with RESTful APIs. One important feature of oData is the use of ETags (Entity Tags), which are part of the HTTP protocol and help manage the state of resources. ETags serve as a version identifier for a resource. When a client retrieves a resource, the server sends an ETag in the response. The client can then use this ETag in subsequent requests to ensure that it is working with the most current version of that resource. What is oData.ETag? In Postman, oData.ETag refers specifically to the ETag values used in oData responses. These tags help maintain data integrity during updates. When a client attempts to update a resource, it can include the ETag in the request headers. If the ETag matches the current version on the server, the update proceeds. If not, the server rejects the request, preventing unintended data overwrites. Using oData.ETag in Postman Fetching an ETag: When you send a GET request to an oData endpoint, look for the ETag header in the response. For example:GET https://api.example.com/odata/productsThe response might look like this:HTTP/1.1 200 OKETag: “W/\”123456789\”” Updating a Resource with ETag: When you need to update the resource, include the ETag in the If-Match header of your PUT or PATCH request:PATCH https://api.example.com/odata/products(1)If-Match: “W/\”123456789\””Content-Type: application/json {    “name”: “Updated Product Name”} If the ETag matches, the update occurs; otherwise, you’ll receive a 412 Precondition Failed response. Related Features in Postman Conditional Requests: Beyond oData, ETags are useful in REST APIs for conditional requests. You can use If-None-Match to check if a resource has changed before downloading it again, saving bandwidth and time. CORS Preflight Requests: When working with cross-origin requests, browsers may perform preflight checks using OPTIONS requests. Understanding ETags can help in managing these requests effectively, ensuring your API can handle them smoothly. Caching Strategies: Implementing caching with ETags can enhance performance. Postman can simulate caching behavior, allowing you to test how your API behaves when dealing with cached responses. Error Handling: Testing how your API handles errors, such as a mismatched ETag, is crucial for robustness. Postman’s test scripts can validate error responses and ensure that your API behaves as expected. Conclusion Understanding oData.ETag in Postman is essential for developers working with RESTful APIs, especially in scenarios where data integrity is critical. By leveraging ETags, you can ensure safe and efficient data updates, manage caching, and improve your overall API interactions.

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 Wave 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:  Wave Templates plays a significant role in advanced warehouses. Wave Templates are used for shipment of goods for Sales Orders, Transfer Order ship, Or Outbound shipment orders. Also, it is used for Production order and Kanban Orders.  – For my current scenario, I will create a Wave template for a Sales Order.  – Select Wave template type as “Shipping”. So, when we create the Sales order wave will be created.  – There is option to Automatically create the Wave.  – Following setup I have enabled.  – Automate Wave creation.  – Process wave at Release to warehouse.  – Process wave automatically at threshold.  – Automate wave release.  – The following basic methods are needed to complete sales order transactions.  – Also, we need to do regenerate methods step to enable methods on wave templates.  – Click Regenerate methods.  Now, Wave Templates are ready to use in Advance Warehouse process.  That’s it for this blog!!  How to use these Wave Templates in actual transactions will be discussed going forward in the blog series.  Next in the Blog series:  How to set up Worker in Advance warehouse management in D365.  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 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 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

Introduction In today’s business environment, Companies must adhere to various financial reporting standards. These standards are essential for fostering investor confidence, ensuring regulatory compliance, and supporting international expansion. Depending on their operational scope, some organizations are required to comply with multiple reporting frameworks, often necessitating the maintenance of multiple books of accounts. Companies need to comply with Financial Reporting Standards – IFRS, UK GAAP, US GAAP, Ind AS, Local GAAP due to reasons like: Compliance with the reporting standards is mandatory for some companies while others may follow them as best practice. There can be scenarios where a company must maintain multiple books of accounts to comply with multiple reporting standards. Example: Company listed on multiple stock exchanges like Infosys, ICICI Bank, TCS (India and US stock Exchange) must prepare financial reports as per Ind AS and as per IFRS. Microsoft Dynamics 365 Finance has the capabilities to meet the financial reporting requirements. How D365 Finance supports Financial Reporting Standards: Thereby, a company can utilize D365 Finance to maintain separate books for Financial Reporting. Conclusion Compliance with various financial reporting standards is not just a regulatory necessity but also a best practice that can enhance investor confidence and facilitate global operations. Microsoft Dynamics 365 Finance simplifies this process by enabling organizations to maintain multiple charts of accounts, set up parallel posting layers, and customize financial reports to meet different regulatory standards. By leveraging the comprehensive capabilities of D365 Finance, businesses can efficiently manage their financial reporting requirements, ensuring compliance across multiple jurisdictions and fostering transparency in their financial operations. 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 many businesses purchase is common & important function. & for purchase department, agreement is important feature. In D365 we have different types of agreements. i.e. Purchase agreement & Trade agreement. Both agreements have its benefits. In this blog will go through overview of purchase & trade agreements in D365 & setup of Purchase agreement in D365 of type Product quantity commitment & Product value commitment. In D365 we can create Purchase agreements for blanket orders to buy certain fixed quantity of item from specific vendor within specified time. Whereas 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 quantity commitment is setup when there is commitment to buy fixed quantity of item from specific vendor over fixed period, so vendor will provide special purchase price for that quantity over defined period. For example, purchaser have committed to buy 1000 quantity of 1 SKU of luggage bag from vendor A over next 1 year then vendor will offer special price of 2000 instead of original price of 3000. Product value commitment is setup when there is commitment to buy fixed amount of specific item from specific vendor over fixed period & vendor provide discount%. For example, purchaser have committed to buy 1 SKU of luggage bag from vendor A worth 1million over next 1 year then vendor will offer 15% discount for same. 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 SKU’s 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: Trade agreement for Purchase price is used to define purchase price of item from specific vendor or group of vendors. The price defined in trade agreement will be reflected in purchase order automatically. Trade agreement for Line discount for purchase is used to define discount on purchase price of item. can setup different types of discounts i.e. Fixed amount, percentage discount or for quantity range. Trade agreement for Multiline discount for purchase is also used define discount on purchase price of item but in multiline discount system will consider quantity of specified item available on multiple lines in purchase order to decide discount percentage. For example, If we have same range for line & multiline discount of 5% for 1-101 & 10% for 101-501. When Purchase order has 2(or multiple lines) of same item. i.e. 1st line has 50pcs & 2nd line has 70pcs. So, in case of Line discount each line will get discount of 5% even though total quantity is greater than 100. But in case of Multiline discount, discount applied will be 10% as total is greater than 100, as it considers total of multiple line. Trade agreement for Total discount for purchase is used to define discount percentage for total purchase order level & not at line level. Also note that, if both purchase agreement & trade agreement are defined for same combination of vendor & item, then Purchase agreement gets precedence / priority over trade agreement. Problem statement: In this scenario we need to setup Product quantity commitment & Product value commitment type of purchase agreement for vendor. Solution steps: 1 – Will create purchase agreement for Product quantity 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-000001) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Product quantity 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 number – P-000003, Quantity – 1000, Unit price – 3000 & 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. 1.4 Confirm purchase agreement. 1.5 Now create new purchase order. Go to Procurement & sourcing -> All purchase orders 1.6 New -> Select Vendor -> Select above created Purchase agreement -> Ok. 1.7 Add Item mentioned in purchase agreement, in this case it is P-000003 & required Quantity 500 in purchase order, price will be automatically taken from purchase agreement. 1.8 We can check which agreement is linked, click on Update line -> Purchase agreement -> Attached. 1.9 Similarly, In Purchase agreement also same is reflected. 2 – Will create purchase agreement for Product 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-000001) -> Purchase agreement classification -> Blanket purchase agreement -> Default commitment -> Product 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 number – P-000003, Net amount – 50000, Discount percentage – 10 & 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 … Continue reading Understanding Purchase & trade agreements in D365 – Part 1 →