Lot No. field not in value entry table but allowed as filter.

(8) Share

Report

Posted on by TM-17111134-0

Hello all,

After a request of a customer for a report with specific lot filtering I stubbled upon this following situation.

The current Version of the Base Application is 26.5 and I found the exact same behavior in the 27.0

I was able to filter the Value Entries table with lot no of my choosing.

Example:

But when I tried to replicate this in my reporting logic and I found out that Lot No. is actually not a field in the Value Entry Table (5802). I aslo checked the page Value Entries (5802) and still there wasn't a lot no field there. I checked the filtering I did through the UI and it was correct. I know how to get around this, by using a get method on the Item ledger Entry table with the Item Ledger Entry No. field that I have in value entries.

My question still remains though. How is this possible? How can I filter a table with a field that it's not precent on the table and actually get correct results? Is it a bug? Is it a feature? If it's a feature how is it done? I would really like to replicate it. Any thoughts?

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (5)

Answers (1)

Suggested answer

Teagen Boll 663 on at

Like (4)

Report

You would have to filter the Value Entries table on the Item Ledger Entry "Entry No." field or the reverse of that like you've already done. That's the only way to link them. I usually pull this data to power BI or other reporting tools and build a report that way instead.

Was this reply helpful? Yes No
Suggested answer

Aman Kakkar 2,319 on at

Like (3)

Report
Hi @TM-17111134-0,

You’re absolutely right — you normally cannot filter on a field that doesn’t exist in the underlying table. Since Lot No. is not part of the standard Value Entry (5802) table, filtering on it should not be possible unless something else is extending the table.

If Lot No. is filterable and working correctly, then the field must come from:

A custom table extension

A partner/ISV app

A localization extension

Please check whether you have any custom extensions or ISV/third-party apps installed that may extend table 5802 with a Lot No. field.

Hope this helps.

Aman K

Was this reply helpful? Yes No
Verified answer

Jainam M. Kothari 15,639 Super User 2025 Season 2 on at

Like (2)

Report
Hello,

This is not a bug—it’s a feature of the Business Central filtering engine. When you filter the Value Entries page by Lot No., the system is actually applying a flow filter or a virtual join behind the scenes.

The Value Entries page includes a FlowField or a linked filter to the Item Ledger Entry table, which does have the Lot No. field.

So, even though the physical table (5802) doesn’t store Lot No., the page definition allows filtering through related tables using FlowFilters and keys.

In a Summary:

The UI filter works because the page is designed to expose fields from related tables via FlowFields or temporary joins.

Your AL report logic doesn’t automatically replicate this because it queries the raw table, not the page metadata.

To replicate this, you need to use the same relationship: join Value Entry with Item Ledger Entry on Item Ledger Entry No. and apply the Lot No. filter there.

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

YUN ZHU 95,395 Super User 2025 Season 2 on at

Like (1)

Report

Hi, Additionally, you can check the field number; if it exceeds 50,000, then it's a custom field.

Thanks

ZHU

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 5,789 on at

Like (1)

Report

Hello,

If you want to expose Lot No. yourself, the easiest way is to use Analyze and Add related fields, which uses the same implicit join the page relies on.
For AL reports or queries, you still need to manually join to Item Ledger Entry.

Regards,
Oussama Sabbouh

1 people found this reply helpful.

Was this reply helpful? Yes No