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

If you are working with SSRS reports in Dynamics 365 CRM, you may have to run or use the report for a single selected record, depending on your need. In this blog, I will explain how to run a report on a selected record in CRM. Running a report on a selected record is also referred to as prefiltering, so let’s first understand what prefiltering is in an SSRS Report.  What is Prefiltering in an SSRS Report?  Prefiltering in an SSRS Report is the process of applying filters before data is retrieved from the data source. It limits the dataset to include only the relevant records by incorporating conditions directly into the query or stored procedure used to fetch data for the report. It only shows relevant data that is needed for the reporting.  To add prefiltering to an SSRS report, follow these steps:  – First, identify the entity you want to run the report for. If the same report needs to be run on multiple entities in CRM, you will need to add the prefiltering condition to all required entities.   – For example, I have considered this project entity   <entity name=”msdyan_project” enableprefiltering=”1″ prefilterparametername=”Parameter1″>  enableprefiltering = “1” specifies that the data for ‘msdyan_project’ will be filter before report is shown for user.  – When running the above query, a parameter named “Parameter1” will be created automatically in Visual Studio.  – Now, publish the SSRS report to the desired environment and add the required field to the related project field to the related record type and you are all set.  Conclusion  Running an SSRS report on a single CRM record is an effective way to display relevant data while ensuring the report remains context sensitive. In this blog, we have provided a step-by-step guide to adding a prefilter in your SSRS report.  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

If you are a decision maker at an organization and looking to strategize the information at your organization and how the systems should source information from one to another, then this post is for you.  Systems for source of truth at the organization is the question you are looking to get answered.  Dynamics 365 Applications involved for Professional Services firms  Let’s break down the systems from Dynamics 365 Application stack-standpoint –   Sales and Project Management  If you are a Professional Services firm in Construction, Engineering, Accounting, IT Services etc. and you have a Sales cycle running from Opportunity generation all the way to Project and Resource Management, then you need Dynamics 365 Project Operations – below is what Project Operations handles –   Accounting  Dynamics 365 Project Operations itself isn’t designed as an Accounting platform – it can create up to Pro-forma Invoices. But here’s to consider some options for Accounting –   Marketing  Marketing is a key aspect for an organization which primary deals with data like Accounts and Contacts – Here are some options to look out for –  HRMS  Maybe you are coming from an existing HR platforms, but here are some thoughts –   Tying it all together  As you’ve seen so far, the source of truth being Dynamics 365 Project Operations or core CRM application because of its flexibility, it is pivotal to source data from this system to other systems and all CRUD operations are tied to Project Operations upon integration.  Other systems are then used to perform their respective operation and send updates back to Project Operations through integration.  Conclusion  Making Dynamics 365 Project Operations as source of truth works for our customers as they find the information clean, consistent and available for correct reporting through just one system.  This gives a true view of the organization without having siloed systems which result in inconsistencies in data and information mismatch if integrations are not architected correctly. Making a system as source of truth gives you improved accuracy and trust in your organizations’ data and drives efficency in the longer run.  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 modern development workflows, maintaining consistency across build pipelines is crucial. A well-organized build process ensures reliability and minimizes repetitive configuration. For developers using YAML-based pipelines (e.g., Azure DevOps or GitHub Actions), template extension is a powerful approach to achieve this. This blog explores how to use YAML templates effectively to manage build stages for multiple functions in your project. What is Template Extension in YAML? Template extension allows you to define reusable configurations in one place and extend them for specific use cases. Instead of repeating the same build steps for every function or service, you can create a single template with customizable parameters. Why Use Templates in Build Pipelines? – Scalability: Add new services or functions without duplicating code. – Maintainability: Update logic in one place instead of modifying multiple files. – Consistency: Ensure uniform processes across different builds. Step-by-Step Implementation Here’s how you can set up a build pipeline using template extension. 1. Create a Reusable Template A template defines the common steps in your build process. For example, consider the following file named buildsteps-template.yml: parameters: – name: buildSteps # the name of the parameter is buildSteps type: stepList # data type is StepList default: [] # default value of buildSteps stages: – stage: secure_buildstage pool: name: Azure Pipelines demands: – Agent.Name -equals Azure Pipelines x jobs: – job: steps: – task: UseDotNet@2 inputs: packageType: ‘sdk’ version: ‘8.x’ performMultiLevelLookup: true – ${{ each step in parameters.buildSteps }}: – ${{ each pair in step }}: ${{ pair.key }}: ${{ pair.value }} 2. Reference the Template in the Main Pipeline This is your main pipeline file: trigger: branches: include: – TEST {Branch name} paths: include: – {Repository Name}/{Function Name} variables: buildConfiguration: ‘Release’ extends: template: ..\buildsteps-template.yml {Template file name} parameters: buildSteps: – script: dotnet build {Repository Name}/{Function Name}/{Function Name}.csproj –output build_output –configuration $(buildConfiguration) displayName: ‘Build {Function Name} Project’ – script: dotnet publish {Repository Name}/{Function Name}/{Function Name}.csproj –output $(build.artifactstagingdirectory)/publish_output –configuration $(buildConfiguration) displayName: ‘Publish {Function Name} Project’ – script: (cd $(build.artifactstagingdirectory)/publish_output && zip -r {Function Name}.zip .) displayName: ‘Zip Files’ – script: echo “##vso[artifact.upload artifactname={Function Name}]$(build.artifactstagingdirectory)/publish_output/{Function Name}.zip” displayName: ‘Publish Artifact: {Function Name}’ condition: succeeded() Benefits in Action 1. Simplified Updates When you need to modify the build process (e.g., change the .NET SDK version), you only update the template.yml. The changes automatically apply to all functions. 2. Customization Each function can have its own build configuration without duplicating the pipeline logic. 3. Improved Collaboration By centralizing common configurations, teams can work independently on their functions while adhering to the same build standards. Best Practices Final Thoughts YAML template extension is a game-changer for developers managing multiple services or functions in a project. It simplifies pipeline creation, reduces duplication, and enhances scalability. By adopting this approach, you can focus on building great software while your pipelines handle the heavy lifting. If you haven’t already, try applying template extension in your next project—it’s a small investment with a big payoff. 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

Organizations are constantly struggling with the complexities of demand and supply forecasting. The traditional methods, often dependent on manual intervention and assumption-based procurement, are increasingly becoming inefficient. These outdated processes lead to inventory overloads, high holding costs, and a significant backlog of orders, all which hamper business growth and scalability. It’s clear that businesses need a more robust, scalable, and accurate forecasting solution. This is where AI-driven demand and supply forecasting solutions come into play, offering a revolutionary approach to streamline operations and enhance decision-making. The Business Challenges Traditional demand and supply forecasting methods pose several challenges that can hamper business success: These challenges underscore the critical need for businesses to move away from manual methods and towards more advanced, automated solutions that can adapt to the ever-changing market landscape. The AI-Driven Solution To address these challenges, CloudFronts offers an innovative AI-driven demand and supply forecasting solution designed to transform the way businesses operate. Here’s how this solution can revolutionize your business: High-Level Architecture The architecture of our AI-driven forecasting solution is designed to ensure scalability, flexibility, and real-time processing capabilities. Key components include: Benefits of AI-Driven Forecasting Implementing an AI-driven forecasting solution offers numerous benefits that can significantly impact your business: Conclusion As the business landscape continues to evolve, the need for accurate, efficient, and scalable demand and supply forecasting solutions becomes more critical than ever. CloudFronts’ AI-driven forecasting solution not only addresses the inefficiencies of traditional methods but also empowers businesses to thrive in a competitive market. 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

For businesses using Dynamics 365 CRM, creating a customized and automated user experience is essential for improving efficiency. JavaScript empowers developers to tailor form behavior based on user input or specific business logic, making your CRM highly adaptable.  Are you looking to automate form fields and improve usability in Dynamics 365 CRM? This guide will help you understand how to use JavaScript to dynamically control field visibility and behavior.  Research shows that 88% of users are more productive with tailored CRM systems. Automating workflows within Dynamics 365 CRM can reduce user errors by up to 70%, streamlining operations and enhancing user satisfaction.  Dynamics 365 CRM is highly customizable, and using JavaScript to enhance form behavior can significantly improve operational efficiency and user experience. Automating processes like field visibility and data handling minimizes manual intervention and ensures consistency.  At CloudFronts, we have extensive experience implementing Dynamics 365 CRM solutions, tailoring them with custom scripts to meet unique business needs. Through hands-on knowledge, we provide practical insights into achieving optimal CRM configurations.  Setting Up Your Dynamics 365 CRM Environment  – Go to the CRM main page, click Settings > Advanced Settings.  – Select Solutions and create a new solution.  – Provide a meaningful name and include the publisher’s name.  Develop a Web Resource  – After creating the solution, develop a web resource and ensure your code is included in it.  – After writing the code, upload the JavaScript and save it as a web resource in make.powerapps.com.  Write your JavaScript code  We’ll look at two key functions in the provided code: toggleExchangeReturnField and onChangeExhReturnItem. Let’s break them down.  Key JavaScript Functions in Action  Function 1: Toggling Fields Based on User Input  Toggling Fields Based on the Toggle Control  toggleExchangeReturnField: function(executionContext) {      var formContext = executionContext.getFormContext(); // Get the form context      var toggleField = formContext.getAttribute(“cri_rma”).getValue(); // Get the value of the toggle field      if (toggleField == true) {          formContext.getControl(“cf_exchangereturnitem”).setVisible(true); // Show the exchange return item field          formContext.getControl(“cri_rmatype”).setVisible(true); // Show the return type field      }      else {          formContext.getControl(“cf_exchangereturnitem”).setVisible(false); // Hide the exchange return item field          formContext.getControl(“cri_rmatype”).setVisible(false); // Hide the return type field      }  },  The `//` symbol in JavaScript is used to add comments within the code. Comments are helpful for explaining the logic or purpose of the code, making it easier for others (or even yourself) to understand later. However, including comments is optional and not mandatory.  Explanation  executionContext.getFormContext(): This function retrieves the form context, which provides access to the form’s controls and attributes.  formContext.getAttribute(“cri_rma”).getValue(): This gets the current value of the cri_rma field, which is assumed to be a toggle field (a boolean that indicates whether the user has opted for an exchange or return process).  formContext.getControl(“cf_exchangereturnitem”).setVisible(true): Based on the value of the cri_rma field, the cf_exchangereturnitem and cri_rmatype fields are either shown or hidden using the setVisible() method.  Purpose:  This function is designed to hide or show form fields dynamically based on the selection in the toggle field (cri_rma). If the toggle is set to true (i.e., an exchange/return is required), it displays the cf_exchangereturnitem and cri_rmatype fields. Otherwise, these fields are hidden.  Purpose: Dynamically show or hide fields based on a toggle field’s value.  How it works: Retrieves the toggle field’s value and sets the visibility of dependent fields accordingly.  Function 2: Handling Multi-Select Field Changes  Handling Changes in the Exchange Return Item Field  onChangeExhReturnItem: function(executionContext) {      var formContext = executionContext.getFormContext(); // Get the form context      var selectedoptions = formContext.getAttribute(‘cf_exchangereturnitem’)?.getSelectedOption(); // Get selected options from the multi-select field      var exchangeReturnProductDescription = “”;      if (selectedoptions != null) {          selectedoptions.forEach(ele => {              exchangeReturnProductDescription += ele.text + “,”; // Append the text of selected options          })          exchangeReturnProductDescription = exchangeReturnProductDescription.slice(0, -1); // Remove the last comma          formContext.getAttribute(‘cf_exchangereturnproduct’).setValue(exchangeReturnProductDescription); // Set the field value with selected options          formContext.data.save(); // Save the data      }      else {          formContext.getAttribute(‘cf_exchangereturnproduct’).setValue(null); // Reset the field if no options are selected      }  }   The `//` symbol in JavaScript is used to add comments within the code. Comments are helpful for explaining the logic or purpose of the code, making it easier for others (or even yourself) to understand later. However, including comments is optional and not mandatory.  Explanation  formContext.getAttribute(‘cf_exchangereturnitem’).getSelectedOption(): This retrieves the selected options from the multi-select field cf_exchangereturnitem. This field likely holds a list of items that the user can select for return or exchange.  exchangeReturnProductDescription += ele.text + “,”;: For each selected option, the code concatenates the text (name) of the item with a comma to build a string of product descriptions.  formContext.getAttribute(‘cf_exchangereturnproduct’).setValue(exchangeReturnProductDescription): The concatenated string of selected items is then assigned to the cf_exchangereturnproduct field. This could be a text field that lists the products selected for exchange or return.  formContext.data.save();: After updating the field, the form data is saved to ensure the changes are persisted.  formContext.getAttribute(‘cf_exchangereturnproduct’).setValue(null);: If no items are selected, the field value is reset to null.   The most crucial step is to add the lines of code within the field. Above all, we need to ensure that the function is added to the form properties. This process will be demonstrated below.  Purpose: Builds a comma-separated list of selected items and updates a designated field.  How it works: Gathers user selections and updates the field in real time, saving changes instantly.  Final Code for Execution  Binding the JavaScript Functions to Form Events  – Open the desired form in your solution at make.powerapps.com and select Entities > Forms.  – Add the JavaScript web resource to Form Properties.  – Under Form Libraries, click Add, select the JavaScript Web Resource you created earlier, and click OK.  Bind the toggleExchangeReturnField and onChangeExhReturnItem functions to relevant field events  – In the Form Editor, select the field (e.g., a text field or lookup) for which you want to trigger the OnChange event. – In the Field Properties window, go to the Events tab.  – Under OnChange, click Add to create a new event handler.  – Select the Library … Continue reading Enhancing Dynamics 365 Forms with JavaScript: Real-Time Field Visibility and Multi-Select Handling →

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

This guide provides a step-by-step walkthrough for integrating Shopify with Business Central (OnCloud). The integration focuses on synchronizing key aspects such as inventory, product details, and order information to enable efficient management of your Shopify store directly from Business Central. With this integration, you can streamline your eCommerce operations and ensure real-time data alignment between both platforms. Pre-requisites: Before beginning the integration, ensure you have the following: Steps for Shopify and Business Central Integration 1. Create an Account on Shopify – Go to Shopify Admin and create your account. – Shopify offers a 3-day free trial, so you can explore the platform before committing. 2. Access the Shopify Dashboard – After successfully creating your Shopify account, you’ll be directed to the Shopify dashboard. – From here, copy the Shopify store URL, as you’ll need it later during the integration with Business Central. 3. Navigate to Business Central – Open Business Central and search for “Shopify Shops” in the global search bar. – Click on New to add a new Shopify shop. 4. Enter Shopify Shop Information – In the new Shopify shop creation screen, enter a unique Code for the shop. – Paste the Shopify URL (copied from step 2) into the required field. 5. Set Shopify Location – In Business Central, go to Shopify Location settings. – Select the relevant location for the shop. 6. Set Stock Calculation – Choose Free Inventory for Stock Calculation. This option ensures that your available inventory is always in sync with Shopify. 7. Add Products in Business Central – First, click on the Products section in Business Central. – Then, click on Add Items to begin adding products to be synced with Shopify. 8. Sync Inventory – Set the Sync Inventory field to True by enabling the corresponding boolean field. – Enter an appropriate Item Category Code for the products, then click OK to confirm. Optional: Sync Product Images – If you wish to sync product images between Shopify and Business Central, select the Sync Item Images to Shopify option. – By enabling this setting, the images of your items will also be synchronized when the products are added to Shopify. 9. Inventory Sync in Shopify – After completing the previous steps, your inventory will be successfully synced from Business Central to Shopify. Any changes made to stock levels in Business Central will now automatically update in Shopify. 10. If you want to sync shopify to business central go to Shopify Shop Card > Select “From Shopify” in Sync Item. 11. After that go to Synchronization and click on sync products By this if you had added product in shopify it will get sync to business central. 12. Customer Synchronization – You can also synchronize customer information between the two platforms. – For example, once you sync, you’ll see that Meagan has been successfully synchronized to Shopify. 13. View Your Online Store – Now you can view your online store and see your products live on Shopify. Theme Customization in Shopify The look and feel of your Shopify store is important in building a strong brand presence. Shopify offers a variety of customizable themes that you can select and edit to match your brand’s identity. How to Select a Theme: How to Set Up Payments on Shopify? Shopify Payments is an integrated payment gateway that simplifies the transaction process for your Shopify store. Here’s how to set it up to ensure your customers can make secure payments directly on your store. Important Points to Consider Before Setting Up Shopify Payments: – Bank Account Location: Ensure that your bank account is in the same country as your Shopify store. – Enable Two-Step Authentication: For enhanced security, activate two-step authentication before setting up Shopify Payments. – Transaction Fees: Be aware that Shopify Payments charges fees for each transaction, which vary depending on your pricing plan. – Minimum Payout Threshold: Shopify Payments does not process payouts below $1, £1, or €1. These smaller amounts will be added to the next payout that meets the threshold. Did You Know? For U.S.-based stores, Shopify Payments incurs a 1% fee for cross-border transactions (for credit card payments made with cards issued outside the U.S.). Step-by-Step Guide to Setting Up Shopify Payments Step 1: Set Your Store Currency Before you begin, establish the currency for your store. This currency may differ from that of your bank account. Changing the store currency after setup will require contacting Shopify Support. To set your currency: – Navigate to Settings > General > Store defaults > Currency display. – Click on Change store currency and select your preferred currency. – Click Save to implement the changes. Step 2: Access Payment Settings Once you’ve set your store currency, return to the Settings menu and choose the Payment option to initiate the payment setup process. Note: It is essential to complete your Shopify Payments account setup within 21 days of your first sale. This includes providing your business and banking details. For merchants located in the European Union or Hong Kong, setting up Shopify Payments is necessary to accept customer payments. Step 3: Activate Shopify Payments To enable Shopify Payments, you first need to create a Stripe account. Then: – Navigate to the Payment settings page in Shopify. – Click the Activate button for Shopify Payments. If you’re transitioning from another payment provider, Shopify offers an easy way to make this switch. Step 4: Select Your Business Type During the activation of Shopify Payments, you must identify your business type: – Individual: For sole proprietors who haven’t formally registered their business. – Registered Business: For businesses operating under a registered name, such as a corporation, LLC, or partnership. – Non-Profit: For organizations that are officially recognized as non-profit entities. Step 5: Designate an Account Representative Setting up Shopify Payments requires appointing an account representative. This individual, typically the owner, senior executive, or director, must possess the authority to make decisions within the business. Their role is crucial for verification with Shopify’s banking partners. Step 6: … Continue reading Seamlessly Integrating Shopify with Business Central: A Comprehensive Guide →