D365 F&O Changing Storage & Tracking dimensions group in Product List & Released Products

(2) Share

Report

Posted on by Dolly Chauhan

Hi,

I wanted to know what are the possible ways to change the Storage & Tracking dimensions group in Product List & Released Products from Frontend & Backend as some of the transactions have been posted recently.

I have business requirement wherein recent loaded products having incorrect storage & tracking dimensions but now we have reupload the products & released products data in D365 FO with correct dimensions group (Storage & tracking dimensions), some of the transactions have already been posted. So how can I remove the products & released products data with correct approach or change the dimensions whatever best option via Frontend & Backend as we have two legal entities and one is already in production and I have to make the changes in another legal entities in Dev env.

Thank you in advance. `

Categories:

Dynamics 365 Supply Chain Management

I have the same question (0)

All responses (6)

Answers (2)

Sohaib Cheema 49,438 User Group Leader on at

Like (0)

Report

I am afraid you would not be able to do it,, while you have posted transactions for the said item. Your options remain creating a new item and disallowing the use of blocked item (that you no more want to transact with).

Was this reply helpful? Yes No
Suggested answer

Yng Lih 1,560 on at

Like (2)

Report

Hi Dolly,

Dimension groups (Storage & Tracking) in D365FO are foundational for how inventory is managed for products.
Once transactions exist (e.g., inventory postings, sales, purchase orders), changing the values is not allowed.

For Products with No Posted Transactions, you can change the Storage/Tracking Dimension Groups from released products.

For Products with Posted Transactions, changing the value is not supported via frontend or standard backend methods.

You will need to create a new product record and then update "Stopped" (i.e. Block) in the "Default Order Settings" for the old product record.

If this information was helpful, kindly mark it as 'Verified'. Thank you. :)

Was this reply helpful? Yes No
Verified answer

sagar_patil 918 Super User 2025 Season 2 on at

Like (1)

Report

Hi,

Try following steps in Dev first before it applies to Production.

1. Make a on-hand qty to zero. (Across all sites and warehouses. No physical, financial, or reserved quantity)

2. Ensure the item isn’t used in any open purchase/sales orders, journals, BOMs, or trade agreements

3. Run Inventory closing

4. Try Changing the Storage/Tracking Dimension Groups

This should work for your case.

Was this reply helpful? Yes No
Dolly Chauhan 68 on at

Like (0)

Report

Thank you @sagar_patil @Yng Lih for the answers. However, in my project we have many released products data so changing it one by one will take lots of time and also, dont know which products were used for transactions. In this scenarios, I have below queries

- how to identify which products are used for transactions ?

- Is there any way to update the dimensions in one go like in batch rather than updating one by one?

It could be helpful if anyone can suggest some options on above.

Thank you in advance.

Was this reply helpful? Yes No
Suggested answer

sagar_patil 918 Super User 2025 Season 2 on at

Like (1)

Report

You need to check the InventTrans table to identify items that have transactions. After that, you can use a data entity to perform a bulk upload.

For example, you can use the Released Product V2 data entity to update the affected items after verifying them in the InventTrans table.

Was this reply helpful? Yes No
Verified answer

Yng Lih 1,560 on at

Like (4)

Report

Hi Dolly,

You can try to use Data Management workspace to create an export project, purpose is to filter which product has on-hand or open transactions; filter the inventory On-hand Physical Inventory > 0, Ordered available >0, etc with multiple exports.

To update, either use Data Management workspace or Excel-add in feature, selecting the data entity Released Product V2 data entity as suggested by @sagar_patil.

If this information was helpful, kindly mark it as 'Verified'. Thank you. :)

Was this reply helpful? Yes No