BC 365 - Bogus Item Attribute Value Mapping Entry

(5) Share

Report

Posted on by Greg Kujawa

352

Using BC 365 SaaS v25.4. One of our users was reporting he couldn't filter by attribute against the items list page. For a specific attribute and a specific value. An error fired that The Item does not exist. Identification fields and values: No.=''.

Looking at Table 7505, I see there is a record in there indeed with a blank No. listed. See screen shot below. I can't apply a configuration package against this to include an existing Item No., since the RowVersion identifier for this specific record isn't included as an available field.

Any suggestions as to how I can fix this?

Categories:

Dynamics 365 Business Central

All responses (6)

Answers (1)

Suggested answer

Ramesh Kumar 3,337 on at

Like (0)

Report

BC 365 - Bogus Item Attribute Value Mapping Entry

Hi Greg,

Please check if you can use Import/Export tool from Insight works. Its helps to corrected the posted entries.

https://dmsiworks.com/apps/import-export-powertool

Thanks

Ramesh

If this was helpful, please check the "Does this answer your question?" box and mark it as verified.
Greg Kujawa 352 on at

Like (1)

Report

BC 365 - Bogus Item Attribute Value Mapping Entry

@Khushbu Rajvi. yes indeed, that was the final solution path. Created a custom action to add to a page. Filters the table for any No. = '' values. Iterates those and deletes them. Still can't figure out how this happened, but if it happens again at least there's a housekeeping function that will take care of it!
Verified answer

Khushbu Rajvi. 14,482 Super User 2025 Season 1 on at

Like (1)

Report

BC 365 - Bogus Item Attribute Value Mapping Entry

Yes, wiping 32K records just to remove one is definitely not ideal. Since you have AL experience, a custom extension is the best approach.
Suggested answer

Jainam M. Kothari 6,025 on at

Like (1)

Report

BC 365 - Bogus Item Attribute Value Mapping Entry

Hello,

To resolve the issue where a user cannot filter by attribute on the items list page due to a blank No. field in Table 7505, you can manually update the record in Table 7505 to include a valid Item No. This can be done by creating a codeunit or using a configuration package to update the No. field. Ensure that the RowVersion identifier is included in the configuration package to allow updates. Additionally, you can use the "Edit in Excel" feature to export the table, correct the blank No. field, and re-import the data.
Greg Kujawa 352 on at

Like (1)

Report

BC 365 - Bogus Item Attribute Value Mapping Entry

The only way that I could remove this one specific record via a configuration package would be if I dumped all other 32K records to an Excel sheet, chose the option to first delete all records in the table, and then applied the sheet. Not the most elegant solution.

Since I have a few years experience with AL development under my belt, I will have to create a custom extension solution for this. Obviously testing out first in a sandbox environment before trying it in production. Too bad this one particular table doesn't have an exposed Entry No. field or something that would appear in a configuration sheet.
Suggested answer

Mansi Soni 1,715 on at

Like (1)

Report

BC 365 - Bogus Item Attribute Value Mapping Entry

Hello, As per my knowledge this issue occurs due to a blank Item No. record in Table 7505 (Item Attribute Value Mapping), preventing filtering on the Items List Page. Since Row Version isn't available in the configuration package, options are limited. You can manually correct the record via AL code or delete the record through the Configuration Worksheet. If the issue persists, contact Microsoft support for backend cleanup.

Hope this answer will help you!

Regards,
Mansi Soni