Integrating Shopify with Dynamics 365 Finance and Operations (FnO) requires structured data management and seamless automation.  This blog covers how to create a setup table and page in FnO to securely store API credentials and endpoints.  In the next blog, we’ll create an automated batch job to push product data from FnO to Shopify, automating product creation on the e-commerce platform. If you are new to this series, you can refer to my blog here for setting up the necessary Shopify components for getting started. Pre-requisites Shopify API credentials (API Key, API Secret, Auth Token)Access to the development environment in Dynamics 365 Finance and Operations. References MS Docs – Create a table MS Docs – Create a form Configuration Step 1: Create the model and project I’m going to be starting from scratch so I’ll create a new model for this. If you already have a model you’ll be using, you can skip this part. Open Visual Studio and click on Continue without Code. Click on Extensions > Model Management > Create Model. Give your model an appropriate name. After everything is selected, click on Next. Give your solution/project appropriate names and click on Create. Step 2: Create Extended Data Types Right click on the project, click on Add > EDT > String. I’ve also created a Label file to store the labels. In the properties of my EDT, I’ll set the string length to 40 and set the label. Similarly I create 2 more EDTs, with the Shopify Auth Token with string size 50. Step 3: Create Table Right click on the project, click on Add > Table. Give it an appropriate name and click on Add. Then, we’ll drag the three EDTs into the fields section of table and set the label to the table. I’ll also add a Parameters Key from the Application Platform Module Next, we create an index on the basis of the ParametersKey (renamed to Key) Drag the Key field into the newly created index and be sure to set the “Allow Duplicates” property to “No” Then we set the necessary properties. This is useful as this will prevent multiple records in our setup table. Then right click on the Methods and click on “New Method” Then add this method logic. Step 4: Create Form Right click on the project, click on Add > Form Give it an appropriate name and click on Add. Right click on the Pattern > Apply Pattern > Table of Contents Right click on the Pattern > New > Tab. Next drag your table onto the Data Sources tab. Select the datasource you just created and set the below properties. Next right click on your Tab and click on “New Tab Page” Right click on the newly created tab page, click on New > Group Right click on the Group > Add > Static Text. Then, right click on the “GeneralTabPage” and add another tab.Inside that, add another tab page (as prescriped by the pattern) and set the pattern of the inner tab page to be “Fields and Field Groups” Inside this tab page, you can directly drag and drop your fields. For the “Shopify Auth Token” set the “Password Style” property to “Yes” Right click on Methods > Override > init. Call the find method of the Integration Parameters in the init method of the form. This ensure that the record is created if it doesn’t exist already. Step 5: Create the menu item for the form Right click on the Project > Add > New Item. In the menu click on User Interface  and select Display Menu item. Give it an appropriate name and click on Add. Assign the appropriate label and set the form we just created into the object field. Step 6: Extending standard menu Go to Application Explorer > Click on User Interface > Menus > right click on “System Administration” and click on “Create Extension” Go to Solution Explorer > Click on the newly created Menu Extension. Right click on the title and click on New > Sub Menu. Give it an appropriate name and an appropriate label. Drag and drop your display menu item into the submenu. Step 7: Configure Security Right click on the project > Add > New Item Go to Security and select Security Privilege. Give it an appropriate name and click on Add. Drag and drop your menu item into the “Entry points” tab of the Security Privilege. Similarly create a Security Role and give it an appropriate name. Then drag your privilege into the role. Set a label to this role. Build the entire project, sync it with database and deploy it. Search for”Assign users to roles” to assign the security role to yourself. Select the role and click on “Manually assign / exclude users” Select your User and click on Assign to role. Click on Modules > System Administration > Shopify Integration > Shopify Integration Parameters. Conclusion This blog demonstrated how to create a setup table and page in Dynamics 365 Finance and Operations for securely storing Shopify API credentials.In the next blog, we’ll focus on handling product updates and synchronization between Shopify and Finance and 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

In the previous part of my blog, I explained about the Credit Only process. In this part of my blog, I will go through the Physical Return process. The Physical return process is determined based on the Disposition Code that is assigned to that Return Order. Disposition Codes in D365 Finance and Operations: Disposition codes in Dynamics 365 Finance and Operations (D365FO) are essential tools used to categorize and manage returned items. These codes help businesses decide what to do with products that customers send back, whether it’s restocking, repairing, or scrapping them. By using disposition codes, companies can streamline their return processes, maintain accurate inventory records, and ensure that returned items are handled efficiently and appropriately. This not only enhances operational efficiency but also helps in improving customer satisfaction by managing returns in a clear and organized manner. Below is the List of Dispositions Codes that are available in D365 FNO: These Disposition codes are available as Standard Functionality in D365 FNO.  You can also create new codes based on the business requirements. In this part of the blog, I will walk you through the Replace Item and Credit Customer scenario. Let’s take a scenario where we have sold 5 items to the customer and after delivery the customer does the Quality check in which 2 products fail due to quality issues. The customer has Scrapped those products on our behalf and now we will provide the customer with the replacement items. For that: Go to Sales and Marketing>Sales Returns>All Return Orders. On the All return orders page click New to create a New Sales Return Order. Select the Customer for which the Return Order is to be created. Enter the Site, Warehouse, RMA number and other details and click OK. In the first part of the blog I created the Return order using the Find Sales Order function so in this part I will directly add the line with negative quantity. In the below screenshot you can see that I have added a line for the Product P-000015 with negative quantity. The next step is to register the Line with the Replace and Credit customer Disposition code. For that click on the Update Line option in the Lines tab then from the drop down click on the Registration option. Then from the Disposition Code drop down select the Replace and Credit Customer option. Then add the registration line then click on Confirm Registration. In the below screenshot you can see the Line status is changed to Registered and the Return order status is changed to Open. Now if you go to the All-Sales Order Page you can see that a New Sales Order is created with the Order type as Returned Order with the Status as Open Order. Now if you open the Sales Order and check the lines the quantity of the line will be exactly same as that of the Return order. The next step is to create a Replacement order as we have selected the Disposition Code of Replace and Credit. For that click on Update Line and Click Registration which will change the Line status from Registered to Expected. As you do this you will notice that the Post Packing Slip button is now disabled, and you can see that the Replacement Order button is now available. As our disposition code is Replace and credit Customer the next step is to create a Replacement Order. For that click on the New Replacement Order button. Add the same site and Warehouse as Return order and click Ok this will create a Replacement Order. After Replacement Order is created go back to the Return Order again and Click Registration and select the Credit disposition code which will Credit the Amount back into the Customer’s account. Now after that Post the Packing slip for the Return order which will change the Return Order status to Received. Then go ahead and Invoice the Return Order from the All-Sales Order page which will again change the Return Order status to Closed. Then go ahead and process the Replacement Sales Order. If you go to the Customer transaction and check, you can see that the Amount is credited back in to the Customer Account. So, this completes the Sales Return Process of Return and Credit to customer. 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

Leasing refers to a contractual arrangement where one party (the lessee) pays the other party (the lessor) for the use of an asset, such as property, vehicles, or equipment, for a specified period. Lease accounting is the process by which companies record the financial impacts of their leasing activities. It has become increasingly important due to new accounting standards that require most leases to be recognized on the balance sheet, enhancing transparency and providing a clearer picture of a company’s financial obligations. Microsoft Dynamics 365 Finance can help companies (CFOs, Finance & accounts team) to set up, operate and manage multiple lease accounting. The work around goes as listed below : 2. i. Create Lease Books: Asset Leasing =>Setup=> Lease Books ii. Define Interest as Expense Type iii. Define Lease rate of interest as Index rate type. iv. Define General Ledger mapping, number sequences and journal types in Asset leasing parameters. 3. Create New Lease in Lease Summary by giving unique Lease ID and update details in Open Books : Lease start date, Vendor Details, Lease Term 4. Run each schedule to ensure that journal entries are made for the chosen period and schedules are generated for the lease period. 5. For any modification in lease terms, termination or revaluation use the Maintain function. 6. Using the Inquiries and Reports – all lease related reports can be used to review and monitor the financial impact of leases. This way the entire lease accounting can be automated whether asset leasing is part or core business of the company. It takes care of the increasing number of leases with comfort and avoids risk of errors and miscalculations. 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

Purchase department plays very crucial role in any company to maintain right inventory at right time & at right price. So to keep business running efficiently purchase orders are released to suppliers accordingly. But there might be changes in confirmed purchase orders due to various reasons & it’s impacts on business will vary case to case basis. It is very important to quickly assess the impact of changes & respond to mitigate the challenges. D365 F&O has released workspace “Confirmed purchase orders with changes” to review and accept changes to confirmed Purchase Orders. This feature is useful to purchase manager, sourcing manager to take quick actions on changes. On this workspace summary is shown for all orders with no. of “Low impact changes”, “High impact changes”, “Impacted downstream orders” sales, production or service orders which will be affected due to changes in purchase orders. List of “All purchase orders with changes”, change details i.e. item no., quantity change, date change, impacted order details as below – Now selected PO is 000039 in “All purchase orders with changes” list in 1st table in lower half. In 2nd table details of changes are provided with item number & changed quantity. As in this PO quantity of item M0007 is reduced from 100 to 10 because of which production order P000169 & P000171 will be affected which is shown in 3rd table in lower half. In 2nd table in upper half M0007 is part of list which are “High impact changes” means changes in this purchase order is going to impact production orders which will affect business. Similarly selected PO is 000038 in “All purchase orders with changes” list in 1st table in lower half. In 2nd table details of changes are provided with item number & changed quantity. As in this PO delivery date of item M0002 is delayed but this change is not going to affect any downstream order. As there are no details in 3rd table in lower half. In 1st table in upper half M0002 is part of list which are “low impact changes” means changes in this purchase order is not affecting any production order or sales order even if it is delayed upto new date. Similarly, all confirmed orders which has changed will be displayed in this list. Once these changes are reviewed by purchase department personnel, they can discuss with suppliers to mitigate the changes. & then confirm the finalized changes by selecting purchase orders on list & click on confirm purchase orders button. Conclusion – Hence using “Confirmed purchase orders with changes” workspace purchase manager can review changes in 1 screen with details of impact on downstream orders & can approve these orders & take required action to reduce the impact on 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

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 Part 3 & 4 blog we have covered setup of Trade agreement for purchase price & line discounts. Let us see difference between Line & multiline discount, if we have same range for line & multiline discount of 5% for 1-101 quantity, 10% for 101-501 quantity & 15% for 501-1001 quantity. When PO has 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 lines. & In line & multiline discount, discount is applied to line. But in total discount, it is applied on total purchase order. In this blog will go through how to setup Trade agreement line discount for Multiline discount & Total discount functionality in trade agreement. Problem statement – In this scenario we need to setup trade agreements for Multiline discount & Total discount functionality in trade agreement. Solution steps – 1 – Will setup trade agreement for Multiline discount 1.1 As discussed in previous blog (Part 3) we have already created Trade agreement journal names; we can use same for this blog. For those who have not gone through blog part 3 can follow below steps Create Trade agreement journal names – Go to Procurement & Sourcing -> Setup -> Prices & discounts -> Trade agreement journal names New -> Name -> Pur Disc -> Description -> Purchase discount -> Relation -> Line disc. (purch.) -> Save. 1.2 & Enable parameters – Go to Procurement & sourcing -> Setup -> Prices & discounts -> Activate price/discount Enable all parameters for Multiline discount. Item group 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.3 Create Item group & assign it to items. Go to procurement & Sourcing -> Prices & discounts -> Price/discount group -> Item discount group -> New -> Price groups -> 01 -> Name -> High Margin -> Price/discount group type -> Multiline discount group New -> Price groups -> 02 -> Name -> Low Margin -> Price/discount group type -> Multiline discount group 1.4 Go to Released products -> respective item -> Purchase Tab -> Multiline discount group -> 01 1.5 Enable Multiline discount – Procurement & Sourcing -> Setup -> Procurement & sourcing parameters -> Prices -> discounts -> Line+Multiline 1.6 Create Trade agreement – Procurement & sourcing – Trade agreement journals -> New -> Name -> Pur disc -> Default relation -> Multiline disc. (purch) -> Lines -> Relation -> Line disc. (Purch.) -> Party code type -> Table -> Account selection -> VEN-000003 -> Product code type -> Group -> Item relation -> 01 -> Unit -> Pcs -> From -> 1 -> To -> 101 -> Unit -> Pcs -> Details (Fast tab) -> Discount percentage 1 -> 5 -> Add line -> From -> 101 -> To -> 501 -> Unit -> Pcs -> Details (Fast tab) -> Discount percentage 1 -> 10 -> Save -> Post 1.7 Create PO – For respective vendor & item. Multiline discount will not reflect automatically. 1.8 To activate discount click on – Purchase (Action pane) – Calculate – Multiline discount. Then discount will be calculated. 2 – Will setup trade agreement for Total discount 2.1 Enable parameters – Go to Procurement & sourcing -> Setup -> Prices & discounts -> Activate price/discount Enable all parameters for Total discount. Total discount will be applicable for all items. 2.2 Create Trade agreement – Procurement & sourcing – Trade agreement journals -> New -> Name -> Pur disc -> Default relation -> Total disc. (purch) -> Lines -> Relation -> Line disc. (Purch.) -> Party code type -> Table -> Account selection -> VEN-000004 -> Details (Fast tab) -> Discount percentage 1 -> 5 -> Save -> Post 2.3 Create PO for respective vendor. Multiline discount will not reflect automatically. 2.4 To check Total discount go to Purchase order (Action pane) – Totals 2.5 To activate discount click on – Purchase (Action pane) – Calculate – Total discount. Then discount will be calculated. 2.6 Go to Purchase order (Action pane) – Totals, total discount of 5% (as defined in trade agreement) is reflecting in Total discount field. With this blog we have covered various aspects of Purchase & trade agreements. 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

Ensuring smooth and efficient operations in Finance and Operations (F&O) is crucial for success in business environment. Many teams struggle with deploying extensions effectively, leading to delays and complications. Have you ever faced challenges when deploying an extension to UAT in F&O? In this blog post, we promise to provide you with a clear, step-by-step guide that will simplify the deployment process, enabling you to achieve seamless integration and improved performance. Did you know that 70% of software deployment failures can be traced back to inadequate preparation and planning? By following our guide, you can significantly reduce the risk of errors and ensure a successful deployment. Prepare the Package – Ensure the logic or customization is thoroughly developed and tested in a development environment. – Compile the solution into a deployable package. Export the Package – Export the compiled package from Visual Studio or another integrated development environment (IDE) By Navigating it to Dynamics 365-> Deploy->Create Deployment Package – The package should include all necessary components (like all customizations models). – Select the File location where you wish to store Deployment Package. Upload to Asset Library – Log into Microsoft Dynamics Lifecycle Services (LCS). – Navigate to the Asset Library section. – Click on Import Package and click on New Button, give name and description and upload the newly created deployable package. – Wait for the upload process to complete. Select the Target Environment (UAT) – Choose the project linked to your UAT environment in LCS. – Go to the Environment Details of the UAT instance. Apply the Package to UAT – In the UAT environment’s details page, select Maintain and click on Apply Updates. – Choose the package you uploaded from the Asset Library. – Confirm the deployment request. Monitor Deployment – Track the deployment progress in LCS. – If successful, the package will be applied to the UAT environment. Validate the Deployment – After deployment, test the UAT environment to ensure the new logic works as expected. – Run key processes to validate the customizations and confirm no errors. Resolve Issues if Necessary – If there are any deployment errors or issues, review the error logs and fix them before re-deploying. – Make sure to thoroughly test before proceeding with the next environment (production). Conclusion Deploying logic to UAT in Finance and Operations (F&O) is a critical step in ensuring that your customizations and new features work as expected before going live. By following these steps from package preparation to validation you can streamline the process and minimize deployment risks. 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

System updates are crucial for keeping systems secure, functional, and up to date with the latest technology advancements and user needs. They are typically provided by software developers, manufacturers, or service providers, and users are often encouraged or required to apply them regularly. System updates are essential for several reasons: One famous story of a catastrophic incident caused by a failure to update a system is the Equifax Data Breach of 2017. Here’s what happened: The Incident: In 2017, Equifax, one of the largest credit reporting agencies in the U.S., suffered a massive data breach that exposed the personal information of over 147 million people. The data leaked included sensitive details like Social Security numbers, birth dates, addresses, and in some cases, credit card information. Cause: The breach occurred because Equifax had failed to apply a critical security patch to a known vulnerability in Apache Struts, an open-source web application framework used in one of their online portals. The vulnerability had been identified and a patch was made available in March 2017, but Equifax did not apply the patch in time, leaving the system exposed. Hackers exploited this known vulnerability in May 2017, and over the next few months, they accessed Equifax’s systems and stole massive amounts of personal data. It wasn’t until July 2017 that the breach was detected, and Equifax publicly disclosed the breach in September 2017. Impact: The consequences were severe: Lesson: This breach became a stark example of why system updates and security patches are critical. A failure to update systems, even with known vulnerabilities, can lead to disastrous consequences, including financial loss, reputational damage, and exposure of sensitive information. Microsoft Dynamics 365, which includes Finance and Operations, has around 500,000 users worldwide as of 2024.With four service updates released each year and roughly one quality update each month, it is crucial for organizations to stay current with the latest features and security enhancements to ensure optimal performance and protection. I am confident that this article will highlight the importance of system maintenance and upkeep. References Details Proactive Quality Updates (PQUs) are automatic updates that bring important bug fixes and new features quickly, without interrupting your work.Delivered through Microsoft Dynamics Lifecycle Services (LCS), PQUs are applied in the background, so businesses hardly notice them. Benefits of PQUs Why PQUs Cause Little Disruption If a serious issue (like downtime or slow performance) happens during a PQU, Microsoft will pause the update and work with customers to fix it. If only one customer is affected, they can open a support ticket to stop the update for their environment. When Might PQUs Be Skipped? PQUs cannot be undone once applied. However, Microsoft can turn off specific changes if needed. Service updates are regular system improvements that give you new features without needing major upgrades.They contain both application changes and platform changes that are critical to the service, including regulatory updates.These updates are backward-compatible, meaning your custom code will still work.Microsoft suggests using the Regression Suite Automation Tool (RSAT) to test updates and make sure nothing breaks. How to Manage Service Updates: Four service updates are released by Microsoft annually in February, April, July, and October.You’re required to take at least two updates per year but can take up to four.You can also pause one update at a time for either your sandbox or production environment. Pre-Servicing: For service updates, the preservicing step starts when the update process begins.During this time, Microsoft Dynamics Lifecycle Services (LCS) shows the environment as Preservicing.This means the environment is online and accessible, but no other service actions can be performed.In this step, the system checks for specific errors that could cause the servicing process to fail.If any errors are found, a soft rollback occurs, which means the system goes back to its previous state without a point-in-time recovery (PITR).To resolve the issues, you can check the environment’s history logs for the errors and make necessary fixes before trying to update again. Post-Servicing: During the post-processing step after offline servicing is complete, the environment status in LCS is marked as Post-servicing.This means that any index creation or changes that couldn’t be done during offline servicing will now occur while the system is online.Users can still access the environment and continue their regular activities, but performance might be slower due to the updates being applied. However, users will not be able to cancel existing service requests or start new ones during this time. Notifications: You will receive several notifications about Microsoft Dynamics updates: Conclusion By keeping your system up to date with these automatic updates, you’ll enjoy new features, regulatory improvements, and better performance—all without the hassle of big upgrades. If all this feels overwhelming, feel free to reach out so we can help you getting this set up and manage it for you! Taking action now will lead to better user experience, minimal disruption in service and smoother operations for your business. 

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 Part 3 blog we have covered setup of Trade agreement for purchase price & line discount. In this blog will go through how to setup Trade agreement line discount for quantity range & find next functionality in trade agreement. Problem statement – In this scenario we need to setup trade agreements for quantity range & Find next functionality. Solution steps – 1 – Will setup trade agreement for Line discount for Quantity range 1.1 As discussed in previous blog (Part 3) point no. 2.1, 2.2 & 2.3 we have already created Trade agreement journal names & enabled parameters hence we can use same for this blog. For those who have not gone through blog part 3 can follow below steps Create Trade agreement journal names – Go to Procurement & Sourcing -> Setup -> Prices & discounts -> Trade agreement journal names New -> Name -> Pur Disc -> Description -> Purchase discount -> Relation -> Line disc. (purch.) -> Save. & 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 supplier (based on vendor group) then need to enable this parameter. Item parameter Yes for All vendors means if item has same price for all suppliers then need to enable this parameter. 1.2 Create trade agreement journal. Go to Procurement & Sourcing -> Prices & discounts -> Trade agreement journals Create new journal – Name -> Pur Disc (Created in step 1.1) -> click on Lines to add details 1.3 Enter line details.  Party code type -> Table -> Account selection -> VEN-000001 -> Product code type -> Table -> Item relation -> P-000012 -> From -> 1 -> To -> 101 -> Unit -> Pcs -> Discount percentage 1 -> 5. Kindly note that, discount will be applicable to range excluding last number. In this case it will be excluding 101. 1.4 Then add lines as per range required Party code type -> Table -> Account selection -> VEN-000001 -> Product code type -> Table -> Item relation -> P-000012 -> From -> 101 -> To -> 501 -> Unit -> Pcs -> Discount percentage 1 -> 10. Party code type -> Table -> Account selection -> VEN-000001 -> Product code type -> Table -> Item relation -> P-000012 -> From -> 501 -> To -> 1001 -> Unit -> Pcs -> Discount percentage 1 -> 15 Then validate & post. 1.5 Then create new purchase order with respective vendor (In this case VEN-000001) for respective item (In this case P-000012) discount % will be reflected as defined in Trade agreement. As per above Trade agreement, if quantity is within 1-100 then discount will be 5%. As per above Trade agreement, if quantity is within 101-500 then discount will be 10%. 2 – Will setup trade agreement for Line discount with Next flag enabled 2.1 When we have trade journal with multiple scenarios for same item, “Find next” flag checks the all the applicable scenarios defined in trade agreement. When “Find next” flag is disabled then system checks & use discount with highest level of details. Create trade agreement journal. Go to Procurement & Sourcing -> Prices & discounts -> Trade agreement journals Create new journal – Name -> Pur Disc (Created in step 1.1) -> click on Lines to add details 2.2 Enter line details.  Party code type -> Table -> Account selection -> VEN-000002 -> Product code type -> Table -> Item relation -> P-000009 -> Unit -> Pcs -> Discount percentage 1 -> 5 -> Find next -> Yes Party code type -> Table -> Account selection -> VEN-000002 -> Product code type -> Table -> Item relation -> P-000009 -> From -> 101 -> To -> 501 -> Unit -> Pcs -> Discount percentage 1 -> 10 -> Find next -> Yes Party code type -> Table -> Account selection -> VEN-000002 -> Product code type -> Table -> Item relation -> P-000009 -> From -> 501 -> To -> 1001 -> Unit -> Pcs -> Discount percentage 1 -> 15 -> Find next -> Yes 2.3 Now if Find next parameter is Disable & then if we create PO with quantity 50 then disc will be 5%, quantity 150 then also discount 5% (even though we have given disc of 10% for 101-501) It is because Find next parameter is turned off, so system search for best fit price. Since in 1st line, quantity is not mentioned it is best fit line for all quantities & hence only applies 5% disc. 2.4 Now if we enable Find next parameters in all 3 lines & then if we create PO with quantity 50 then discount will be 5%, quantity 150 then discount 15% (as we have defined discount of 10% for 101-501 & 5% for all quantity) So system finds 2 best possible discounts hence added the same. If quantity 700 then discount 20% & If quantity 1050 then Discount 5%, as we have defined additional discount till quantity 1000. In this blog we completed how to setup of trade agreement line discount for quantity range & next flag. In next blog (Part 5) will cover Multiline discount & Total discount. 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

Excel has over 750 million users worldwide, making it one of the most popular software applications in the world. According to recent studies, 89% of companies use Excel for daily operations, financial modeling, data analysis, and other tasks. Excel is so integral to the financial world that many financial analysts and accountants refer to themselves as “Excel jockeys” or “Excel ninjas.” NASA used Excel in its operations for various calculations related to space missions. Using Excel for manual data entry is much more easier for end users as it provides a familar interface and can be navigated much more quickly.It can also be used for quick minor calculations and formulas. References: Details: For businesses generating large volumes of data, it’s essential to have an efficient system for users to input that data smoothly.  Are you struggling to keep up with your rapidly growing data? A study by Forrester Consulting shows that companies using Microsoft 365 tools like Excel, Word, Outlook, and PowerPoint see a 15-20% boost in employee productivity due to better collaboration and task management. This article will surely inspire you to start using Excel for your organization’s daily operations too! Enabling the Developer Tab in Excel To access advanced features like creating macros, using form controls, or accessing the XML commands in Excel, you’ll need to enable the Developer tab. Here’s how: – In the Developer Tab, click on “Add Ins” – In the pop-up that follows, click on “Store” and search for “Microsoft Dynamics” and click on enter. – Once you get the results as described in the below screenshot, click on “Add.” – Click on Continue. – Go to your Finance and Operations environment. – Go to System Administration -> Setup -> Office App Parameters. – Go to App Parameters and click on “Initialize app parameters” – Go to “Registered applets” and click on “Initialize applet registration” – Go to “Registered resources” and then click on “Initialize resource registration” – Then to test it out, we can go to the “All sales orders” list click on the “Office” icon at the top right and click on one of the “non-obsolete” options. – You can either download it on your own system or you can save it directly from this screen. – When you open the downloaded excel, after enabling editing, you’ll get the following pop-up and data. – You can also use this Excel to create records in the system. – Open the downloaded excel sheet. – Click on “New”. – Add the necessary fields in the newly created rows. – Once done, click on Publish. And we can see back in D365 that we have added some new records in the system via Excel. In conclusion, I firmly believe that using Excel for manual data entry can significantly cut down on unnecessary tasks.If you’re looking to streamline your processes or maximize the potential of your ERP systems, please feel free to reach out.

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