Feedback Edit

Install and set up Inventory Visibility

  • Article
  • 8 minutes to read

This article describes how to install the Inventory Visibility Add-in for Microsoft Dynamics 365 Supply Chain Management.

You must use Microsoft Dynamics Lifecycle Services (LCS) to install the Inventory Visibility Add-in. LCS is a collaboration portal that provides an environment and a set of regularly updated services that help you manage the application lifecycle of your finance and operations apps. For more information, see Lifecycle Services resources.

Tip

We recommend that you join the Inventory Visibility Add-in user group, where you can find useful guides, get our latest updates, and post any questions you may have about using Inventory Visibility. To join, please send email to the Inventory Visibility product team at inventvisibilitysupp@microsoft.com and include your Supply Chain Management environment ID.

Inventory Visibility prerequisites

Before you install the Inventory Visibility, you must complete the following tasks:

  • Obtain an LCS implementation project where at least one environment is deployed.
  • Make sure that the prerequisites for setting up add-ins have been completed. For information about these prerequisites, see Add-ins overview. Inventory Visibility doesn't require dual-write linking.

Note

The countries and regions that are currently supported include Canada (CCA, ECA), the United States (WUS, EUS), the European Union (NEU, WEU), the United Kingdom (SUK, WUK), Australia (EAU, SEAU), Japan (EJP, WJP), and Brazil (SBR, SCUS).

If you have any questions about these prerequisites, contact the Inventory Visibility product team at inventvisibilitysupp@microsoft.com.

Install the Inventory Visibility Add-in

Before you install the add-in, register an application and add a client secret to Azure Active Directory (Azure AD) under your Azure subscription. For instructions, see Register an application and Add a client secret. Be sure to make a note of the Application (client) ID, Client secret, and Tenant ID values, because you'll need them later.

Important

If you have more than one LCS environment, create a different Azure AD application for each of them. If you use same application ID and tenant ID to install the Inventory Visibility Add-in for different environments, a token issue will occur for older environments. As a result, only the last installation will be valid.

After you register an application and add a client secret to Azure AD, follow these steps to install the Inventory Visibility Add-in.

  1. Sign in to LCS.

  2. On the home page, select the project where your environment is deployed.

  3. On the project page, select the environment where you want to install the add-in.

  4. On the environment page, scroll down until you find the Environment add-ins section in the Power Platform integration section. There, you can find the Dataverse environment name. Confirm that the Dataverse environment name is the one that you want to use for Inventory Visibility.

    Note

    Currently, only Dataverse environments that were created by using LCS are supported. If your Dataverse environment was created in some other way (for example, by using the Power Apps admin center), and if it's linked to your Supply Chain Management environment, you must first contact the Inventory Visibility product team at inventvisibilitysupp@microsoft.com to fix the mapping issue. You can then install Inventory Visibility.

  5. In the Environment add-ins section, select Install a new add-in.

    Environment page in LCS

  6. Select the Install a new add-in link. A list of available add-ins appears.

  7. In the list, select Inventory Visibility.

  8. Set the following fields for your environment:

    • AAD application (client) ID – Enter the Azure AD application ID that you created and made a note of earlier.
    • AAD tenant ID – Enter the tenant ID that you made a note of earlier.

    Setup add-in page

  9. Agree to the terms and condition by selecting the Terms and conditions checkbox.

  10. Select Install. The status of the add-in is shown as Installing. When the installation is completed, refresh the page. The status should change to Installed.

  11. In Dataverse, select the Apps section in the left navigation, and verify that the Inventory Visibility Power Apps is installed successfully. If the Apps section doesn't exist, contact the Inventory Visibility product team at inventvisibilitysupp@microsoft.com.

Note

If it takes more than an hour to install from the LCS page, then your user account probably lacks permission to install solutions in the Dataverse environment. Follow these steps to resolve the issue:

  1. Cancel the Inventory visibility add-in installation process from the LCS page.

  2. Sign in to the Microsoft 365 admin center and make sure that the user account you want to use to install the add-in has the "Dynamics 365 Unified Operations Plan" license assigned to it. Assign the license if needed.

  3. Sign in to the Power Platform admin center using the relevant user account. Then install the inventory visibility add-in by doing the following steps:

    1. Select the environment where you want to install the add-in.
    2. Select Dynamics 365 Apps.
    3. Select Install App.
    4. Select Inventory Visibility

  4. After the installation completes, go to back to the LCS page and try again to reinstall the Inventory Visibility add-in.

Set up Inventory Visibility in Supply Chain Management

Deploy the Inventory Visibility integration package

If you're running Supply Chain Management version 10.0.17 or earlier, contact the Inventory Visibility on-board support team at inventvisibilitysupp@microsoft.com to get the package file. Then deploy the package in LCS.

Note

If a version mismatch error occurs during deployment, you must manually import the X++ project into your development environment. Then create the deployable package in your development environment, and deploy it in your production environment.

The code is included with Supply Chain Management version 10.0.18. If you're running that version or later, deployment isn't required.

Make sure that the following features are turned on in your Supply Chain Management environment. (By default, they're turned on.)

Feature description Code version Toggle class
Enable or disable using inventory dimensions on InventSum table 10.0.11 InventUseDimOfInventSumToggle
Enable or disable using inventory dimensions on InventSumDelta table 10.0.12 InventUseDimOfInventSumDeltaToggle

Set up Inventory Visibility integration

Once you've installed the add-in, prepare your Supply Chain Management system to work with it by doing the following steps.

  1. In Supply Chain Management, open the Feature management workspace, and turn on the following features:

    • Inventory Visibility Integration – Required.
    • Inventory Visibility integration with reservation offset – Recommended but optional. Requires version 10.0.22 or later. For more information, see Inventory Visibility reservations.

  2. Go to Inventory Management > Set up > Inventory Visibility Integration parameters.

  3. Open the General tab and make the following settings:

    • Inventory Visibility endpoint – Enter the URL of the environment where you're running Inventory Visibility. For more information, see Find the service endpoint.
    • Maximum number of records in a single request – Set to the maximum number of records to include in a single request. You must enter a positive integer less than or equal to 1000. The default value is 512. We strongly recommend keeping the default value unless you have received advice from Microsoft Support or are otherwise certain that you need to change it.

  4. If you enabled the optional Inventory Visibility integration with reservation offset feature, open the Reservation offset tab and make the following settings:

    • Enable reservation offset – Set to Yes to enable this functionality.
    • Reservation offset modifier – Select the inventory transaction status that will offset reservations made on Inventory Visibility. This setting determines the order processing stage that triggers offsets. The stage is traced by the order's inventory transaction status. Choose one of the following options:
      • On order – For the On transaction status, an order will send an offset request when it's created. The offset quantity will be the quantity of the created order.
      • Reserve – For the Reserve ordered transaction status, an order will send an offset request when it's reserved, picked, packing-slip posted, or invoiced. The request will be triggered only once, for the first step when the mentioned process occurs. The offset quantity will be the quantity where the inventory transaction status changed from On order to Reserved ordered (or later status) on the corresponding order line.

  5. Go to Inventory Management > Periodic > Inventory Visibility Integration, and enable the job. All inventory change events from Supply Chain Management will now be posted to Inventory Visibility.

Uninstall the Inventory Visibility Add-in

To uninstall the Inventory Visibility Add-in, follow these steps:

  1. Sign in to Supply Chain Management.

  2. Go to Inventory Management > Periodic > Inventory Visibility Integration and disable the job.

  3. Go to LCS and open the page for the environment where you want to uninstall the add-in (see also Install the Inventory Visibility Add-in).

  4. Select Uninstall.

  5. The uninstallation process now terminates the Inventory Visibility Add-in, unregisters the add-in from LCS, and deletes any temporary data that is stored in the Inventory Visibility Add-in data cache. However, primary inventory data that was synced to your Dataverse subscription is still stored there. To delete this data, complete the rest of this procedure.

  6. Open Power Apps.

  7. Select Environment on the navigation bar

  8. Select the Dataverse environment that is bonded with your LCS environment.

  9. Go to Solutions and delete the following solutions in the following order:

    1. Anchor solution for Inventory Visibility application in Dynamics 365 solutions
    2. Dynamics 365 FNO SCM Inventory Visibility Applications Solution
    3. Inventory Service Configuration
    4. Inventory Visibility Standalone
    5. Dynamics 365 FNO SCM Inventory Visibility Base Solution

    After you delete these solutions, the data that is stored in tables will also be deleted.

Note

If you restore a Supply Chain Management database after uninstalling the Inventory Visibility Add-in, and then want to reinstall the add-in, make sure that you have deleted the old Inventory Visibility data that is stored in your Dataverse subscription (as described in the previous procedure) before you reinstall the add-in. This will prevent data inconsistency issues that could otherwise occur.

Clean Inventory Visibility data from Dataverse before restoring the Supply Chain Management database

If you have been using Inventory Visibility and then restore your Supply Chain Management database, then your restored database may contain data that is no longer consistent with data previously synced by Inventory Visibility to Dataverse. This data inconsistency can cause system errors and other issues. Therefore, it's important that you always clean all Inventory Visibility data from Dataverse before your restore a Supply Chain Management database.

If you need to restore a Supply Chain Management database, use the following procedure:

  1. Uninstall the Inventory Visibility Add-in and remove all related data in Dataverse, as described in Uninstall the Inventory Visibility Add-in
  2. Restore your Supply Chain Management database, for example as described in Database point-in-time restore (PITR) or Point-in-time restore of the production database to a sandbox environment.
  3. If you still want to use it, then reinstall and set up the Inventory Visibility Add-in as described in Install the Inventory Visibility Add-in and Set up Inventory Visibility integration

Help us understand

We want to learn more about how people use Microsoft's custom Help toolkit. Take the survey (in English) and help us understand: https://forms.office.com/r/A4cUJgjkD1.