Jaa

Troubleshoot Retail data solutions (preview)

  • Artikkeli

Important

Some or all of this functionality is available as part of a preview release. The content and the functionality are subject to change.

This article explains how to resolve potential issues you might experience with Retail data solutions.

Limitations

There are some limitations of the Retail data solutions:

  • Each entity takes approximately five seconds to deploy it in the Lakehouse. Recommend selecting only the required entities while deploying the entities from Industry data model.

  • We're currently restricting only one instance of industry data solution within a workspace. However, you can install the data solutions for different industries into the same folder. For simplicity and management, we recommend that you create one data solution per workspace and create a separate workspace per development environment.

  • After you deploy a specific entity from Retail industry data model, you'll observe that 'long' datatype is getting installed as 'biginteger' and 'date' datatype is getting installed as 'timestamp'. These datatypes aren't supported in Fabric. Currently, only tables containing these column types are impacted by this mapping discrepancy. A temporary workaround is to manually edit the delta tables definition file during the provisioning of the IDM Retail schema to replace all occurrences of 'bigInteger' with 'long', and 'date' with 'timestamp' datatype respectively.

Troubleshoot

Retail data solutions artifact pop up shows late

If you're using Industry Solutions and selected Retail Solutions from the homepage for the first time, the pop-up display might take some time and request you to wait. Subsequent openings are faster.

Customizations are lost if the artifacts are updated or reinstalled

If you deployed a capability from Retail data solutions and made changes or customizations to suit your unique needs, ensure that you manually back up all the artifacts before uninstalling, updating, or reinstalling the capability. The system doesn't retain any customizations made and reinstalls new artifacts.

Partial deployment of a capability due to errors

If you're deploying a capability or an Industry data model and the deployment wasn't successful for all the components in the final step, it could be that some of the artifacts were already deployed while others failed. In this case, we recommend that you delete the entire capability and reinstall it.

Workspace doesn't have the capacity to create new artifacts

Fabric licensing is based on capacity units and storage consumption. If you already consumed the capacity units, you can't deploy any of the capabilities from industry solutions. In this case, identify and delete the workspaces that you no longer need to free up capacity units and storage, or work with your account team to increase the workspace limits. For more information, see licensing for Microsoft Fabric.

Retail industry data model deployment fails due to workspace permissions

Ensure that you are in the correct workspace where you have the admin permissions to deploy the artifacts. If not, switch to the appropriate workspace and deploy the Retail data solutions artifact.

Retail industry data model deployment fails due to large number of entities selected to be deployed

If you selected a large set of entities, it takes approximately 3-5 seconds per entity to deploy. Therefore, be patient or deploy the entities in smaller chunks. For example, if you want to deploy more than 200 entities, consider doing so in smaller batches of 50-100 entities at a time.

Tip

If problem still persists, contact your Microsoft support representative.