I get an error when I use table relation with filters

(5) Share

Report

Posted on by Muaaz Deyab

I get this error when I try to use table relation with filters
Microsoft.Dynamics.Nav.Types.DBLazy it is not the error itself but it is being inserted in the field instead of the value
Can any one help me?

I have the same question (0)

All responses (6)

Answers (1)

Sort by

Suggested answer

IB-29041624-0 1,191 Moderator on at

Like (2)

Report
Copy link

Link copied!

Maybe you can try to share your code, then it is easier to assist you in cases like this.

Or at least elaborate a little more about what you are trying to do and from where?

Was this reply helpful? Yes No
Muaaz Deyab 39 on at

Like (2)

Report
Copy link

Link copied!

I solved this by using OnLookup trigger, still could not figure out what was the problem

but here is the Code

field(5; "Requester"; code[20])

{

DataClassification = ToBeClassified;

TableRelation = Requester.OnBehalf where("User Name" = field(Preparer), Status = const(Approved));

ValidateTableRelation = false;

}

Was this reply helpful? Yes No
GA-27040922-0 4 on at

Like (2)

Report
Copy link

Link copied!

What helped for me is to add this field to the page and then the error didn't happen anymore, could find other solution for this

Was this reply helpful? Yes No
Verified answer

Hallister 11 on at

Like (3)

Report
Copy link

Link copied!
The error is still present in BC24.5.

Steps for reproducing:
Create a table field with a table relation to another table and to a field outside the primary key. The TableRelation must be set to false.
Insert the field into a page object.

Example: field(10; ‘Additional Field’; Code[10]) { Caption = ‘Additional Field’; TableRelation = ‘Location’. ‘Additional Field’; ValidateTableRelation = false; }

If you now try to make a selection via drilldown, you receive the error ‘Microsoft.Dynamics.Nav.Types.DBLazy’

If you use the ‘Show full List’ function for selection, the expected value will be applied.

Solution:
The error can be avoided if the required field is added to the drilldown page of the corresponding table. The field does not even have to be visible.

Example:

pageextension 50000 ‘Location List’ extends ‘Location List’ { layout { addlast(Control1) { field(‘Additional Identifier’; Rec. ‘Additional Identifier’) { ApplicationArea = All; Visble = false; } } } }

I hope I was able to help you with this.
Happy Coding

Was this reply helpful? Yes No
CU06030732-0 6 on at

Like (3)

Report
Copy link

Link copied!

Today, I got the same error in BC25.4 – both OnPrem and Cloud. It's strange that, after all this time, it still poses a problem. I figured out exactly the same workaround and then found this thread. Nice to be confirmed ;-)

Was this reply helpful? Yes No
Suggested answer

Mats Thell 4 on at

Like (2)

Report
Copy link

Link copied!

Sidenote; It is also enough that the field is included in the fieldgroup DropDown instead of DrillDownPageId.
Thanks for pointing out what the issue was.

Was this reply helpful? Yes No

Join the conversation

Community site session details

I get an error when I use table relation with filters

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Winners!

Women in Power Builds Momentum

Congratulations to the July Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates

Community site session details

I get an error when I use table relation with filters

Helpful resources

News and Announcements

Quick Links

Season of Sharing Community Challenge Winners!

Women in Power Builds Momentum

Congratulations to the July Top 10 Community Leaders

Subscribe to this forum!

Select categories

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates