Should I Insert Records into the [Item Attribute Value Mapping] table that don't have a corresponding record in the [Item] table


We transitioned to Dynamics NAV 2018 from another ERP and we have a lot of old items that we didn't want to import to Nav because they were no longer being sold but we still need them for historical reporting. We could import and block them but we want as little clutter as possible on the items list page.

Effectively, I wanted to add item attributes for these items in Nav without setting up an item card and I noticed that Nav will let me import records into the [Item Attribute Value Mapping] table even though the item does not exist as a separate item card. Even though I'm able to do it I wanted to know if it is a good idea or if I am playing with fire.

The only downside to my method that I have seen thus far is that I cannot use the Filter by Attributes button on the items page when trying to filter by an attribute that is assigned to at least 1 non-existent item.

I get the message "The Item does not exist. Identification fields and values: No.=xxx"

Maybe it is better to create a separate table within Nav to hold these items and attributes? Seems like it would require a lot of customization to union the secondary item attributes table with the original for all reports, queries, pages, etc.

Appreciate any advice.

Parents Reply Children
No Data