Dynamics Community Forum Thread Details

AX2012 R3 to D365 FO Self-Service Upgrade – Step 10 Fail: Missing View DimAttributeOMRetailChannel

Hi everyone,

We’re currently performing a self-service AX 2012 to D365 Finance data upgrade using the Data Migration Tool (DMT). The upgrade has reached Step 10 – "Execute Script - PostSync - Wait for batch", but it’s failing with the following error:

Dimension synchronization failed. The backing view DimAttributeOMRetailChannel for the financial dimension 'RetailChannel' does not exist.
Batch task failed: Dimension synchronization failed.

We noticed that the RetailChannel dimension still exists in the DimensionAttribute table, but its corresponding backing view (DimAttributeOMRetailChannel) is missing in SQL.

Has anyone faced this during a Step 10 failure in a self-service data upgrade scenario? What approach worked to resolve it?

We’ve already raised a ticket with Microsoft support, but unfortunately, we haven’t received a helpful resolution yet. Would really appreciate insights from anyone who has encountered and resolved this in past upgrade projects.

Thanks in advance for your support!

Categories:

Dynamics 365 Finance

Microsoft Dynamics AX

You're encountering a Step 10 failure during the self-service upgrade from AX 2012 R3 to D365 Finance due to a missing backing view for the 'RetailChannel' dimension – specifically, DimAttributeOMRetailChannel. This is a known issue in some AX 2012 environments, especially where Retail was previously implemented and then partially removed or where Retail-related dimensions were not fully cleaned up.

✅ Root Cause
The error:
rust
CopyEdit
Dimension synchronization failed. The backing view DimAttributeOMRetailChannel for the financial dimension 'RetailChannel' does not exist.
means that the RetailChannel dimension exists in the DimensionAttribute table but the corresponding view (DimAttributeOMRetailChannel) is missing in SQL, which is required for dimension synchronization to succeed during the upgrade.
This often occurs in environments where the Retail module was either removed or partially uninstalled from AX 2012, but the dimension metadata was left behind.

✅ Solution
You must remove the orphaned financial dimension metadata before the script in Step 10 can succeed.
⚠️ Warning: Make sure to back up the upgraded D365 FO database (UAT or sandbox copy) before running these queries. Never run this directly on production.

🔧 Step-by-Step Fix

Connect to the target upgraded SQL database (the D365 FO database you're upgrading to).
Check if the RetailChannel dimension still exists:

sql
CopyEdit
SELECT * FROM DimensionAttribute
WHERE Name = 'RetailChannel';

If it exists, delete the orphaned RetailChannel dimension manually:

sql
CopyEdit
DELETE FROM DimensionAttribute
WHERE Name = 'RetailChannel';

Also remove any references in related tables (optional, but ensures clean removal):

sql
CopyEdit
DELETE FROM DimensionAttributeValue
WHERE DimensionAttribute IN (
SELECT RecId FROM DimensionAttribute WHERE Name = 'RetailChannel'
);

Restart Step 10 in LCS:
- Go to LCS → Project → Data Upgrade → Step 10: Execute Post-Sync Script.
- Click Resume or Retry the step.

🔄 Alternative (if you're using a custom RetailChannel)
If you're using a custom dimension tied to OMRetailChannel, make sure:

The backing view DimAttributeOMRetailChannel exists in the upgraded D365 FO schema.
If it's missing, you may need to re-add the table/view as part of your customization and regenerate the financial dimensions using DimensionProcessor logic in X++.

But based on your description, it seems the module was removed, and the dimension is no longer relevant.

✅ Final Notes

This kind of issue is not uncommon in upgrades from AX 2012 R3 environments where Retail was installed at some point.
Microsoft typically recommends removing unused or legacy financial dimensions from AX 2012 before exporting the data or before running the DMT.
You're doing the right thing raising a ticket, but this manual cleanup is often the only quick way forward.