Shopify Meets Dynamics 365 Finance and Operations: A Guide to Integration [Part 1]

-


Introduction

The integration of Shopify with Dynamics 365 Finance and Operations (FnO) starts by creating a secure link.
The initial step in this process involves generating an API token within Shopify, serving as the credential for verified communication between both systems.
In this blog I will walk you through the steps to create the API token, facilitating a seamless beginning for your integration.

Pre-requisites

  • Access to the Shopify Admin account with appropriate permissions to create private apps or access custom apps.
  • API access enabled in your Shopify store.
  • A basic understanding of API concepts and authentication methods. [Available in Reference]
  • The URL or endpoint details where the API calls will be directed. [Available in Reference]

    • References

    Configuration

    Step 1: Access the Shopify Admin Portal

    Log in to your Shopify store's Admin account.
    Navigate to Apps from the main menu.


    Step 2: Create a Custom App

    Click on Develop Apps (available under Apps).
    Select Create an App and provide a name (e.g., "Dynamics365_Integration").
    Assign a developer or admin as the app owner.





        

    Step 3: Configure API Scopes

    After creating the app, click on it to open the configuration page.
    Under the Configuration section, define the API scopes required for integration based on your requirements.
    You can change these later if required.
      
    For example:
    • read_orders
    • write_orders
    • read_products
    • write_products
    Click on Save to save the changes.






    Step 4: Generate the API Token

    Once scopes are set, click on the API credentials tab.
    Click Install App to generate the credentials.
    A unique Access Token will be displayed. 
    Copy and securely store this token, as it will not be shown again.
    If you scroll down, you'll also see the API Key and API Secret; store these values as well.





    Step 5: Test the Token

    Use a tool like Postman to test the API token.
    Set up a GET request to an API endpoint (e.g., https://<API KEY>:<API Secret>@<Store Name>.myshopify.com/admin/api/2023-07/products.json).
    Include the token in the header as X-Shopify-Access-Token.
    Verify the response to confirm the token is working correctly.


    Or simply (https://<Store Name>.myshopify.com/admin/api/2023-07/products.json)




    Conclusion

    The API token is your gateway to integrating Shopify with Dynamics 365 Finance and Operations. 
    By following this guide, you’ve taken the first critical step toward seamless data flow between your e-commerce platform and back-office operations. 
    In the next blog, we’ll explore how to configure Dynamics 365 FnO to connect with Shopify and start synchronizing data.

    Comments

    Post a Comment

    Popular posts from this blog

    Using Notifications in Business Central via AL

    -
    Image
    Introduction Notifications in Business Central are alerts that appears in the Notification bar based on User actions. Notifications stack up from top to bottom, lasting until the user dismisses them, including those from sub-pages.  Validation errors are prioritized and shown before other notifications. We can use this to alert the user regarding something without taking all the user's notification towards it, in the way messages or errors do. They also have the option to allow Users to make a corrective action by embedding the action button directly into the notification. Let's see how it works. Source Code Pre-requisites Business Central OnPrem/Cloud. References Notification - Business Central Docs Configuration Here, for an example, I've created one simple page which takes two inputs. 1. The message that is to be shown in the notification. 2. The message to be shown after the User clicks on the action embedded in the notification.     And I have two actions which I'l...
    Read more

    Actionable Error Messages in Business Central

    -
    Image
    Introduction Error handling is an important concept in every technical field.  It helps programs deal with unexpected problems and mistakes smoothly.  It makes sure software works reliably and doesn't crash unexpectedly.  Error handling also helps developers find and fix issues quickly, making the software better for users. Plus, it gives users clear messages when something goes wrong, making their experience smoother. It shows that the team has considered the scenario and has measures in place for it indicating a well designed solution. Microsoft has an amazing document which lists the things to keep in mind for writing resilient code. In Business Central, we have try functions to handle errors and error function to show those errors to the Users.  In this blog, we'll learn how we can enhance the error messages so that the Users can resolve the errors themselves or at the very least we can point them towards where the error is. Pre-requisites Business Central OnPrem...
    Read more

    Configure Gmail SMTP service in Business Central without "Allow Less Secure" setting

    -
    Image
     Introduction Business Central has great email features like sending email, editing it with Rich Text, adding attachments, etc, but to send emails, you'll need to connect it with services like Outlook or Gmail. There is no outlook side configuration that is to be done if you are using Microsoft Outlook however if you are using Google's Gmail then there's a litte change that has happened on the configuration end. Starting May, 2022, Google has removed the "Allow Less Secure Apps" settings from the Google Accounts, which was essential is using Gmail to send emails from Business Central. However, to replace that we have "App Passwords" which we can use instead. Also, just something to keep in mind, Google is going to remove this from the "Google Workspace" accounts as well by Sept, 2024 so it would be wise for you to migrate your configurations to use app passwords. Reference 1.  How to Setup Email in Business Central 2.  Google Support - Less sec...
    Read more