Lookup on data in subforms

[yvesf]

Hello,

Is there a mean to retrieve data from a subform via a lookup field ?
Ex :
I have a company table in which I have a subform employee with firstname, lastname.
I have another table project in which I would like to lookup on employee whatever the company is.
On project table, I create a field project name, and a subform field stakeholders.
The stakeholder subform has a lookup on subform employee. I have got nothing as result of the lookup.
Is it possible to do that, it seems you cannot do that when you use subform mechanism.
Is anyone could confirm that ? is there any workaround ?
Thx and regards,

Yves

[yvesf]

Solved by Kevin. You need to have the browse subform configured exactly for that reason.

[yvesf]

Hello,

How to cascade lookup fields on edit forms and on subforms (mode grid) ?
Cascading select fields on edit form could be done by passing the first field value (company drop down field value ) in the clause where of the second field (employee dropdown field value).You need also to refresh the send select onchange event of the first select field custom tab.
How to perform that on subforms ? with select fields ? and with lookup fields ?
Lookup fields are interesting because of their search ability and are very interesting when dropdown list cannot be implemented due to number of records.
Let me take my example again.
I have got the list of companies that contains 100 + records. Having a such huge list in dropdown list is weird. In the second dropdownlist, same thing : it's the employee's of each company which has 100 + records for most of them. Having lookup fields would be the option.
How to perform that on edit form and on subforms mode grid ?
Many thanks for your help.


Yves

[kev1n]

Basically, a lookup form can be filtered by setting a hash cookie before it's opened.

E.g. in JS:

Code: Select all

nuSetProperty('your_filter', '123');

in the Browse SQL:

Code: Select all

WHERE a_column = '#your_filter#'

[selector]

Basically, a lookup form can be filtered by setting a hash cookie before it's opened.

hey Kevin. But it is also necessary to do this in the onchange event. The problem is that the onchange event is triggered only after saving the form. At least if we talk about Lookup fields.

[kev1n]

Can't you trap the lookup's onclick event and set the Hash Cookie there?

Required nu-version:
Files Version: V.4.5-2023.03.10.03

[selector]

Can't you trap the lookup's onclick event and set the Hash Cookie there?

Required nu-version:
Files Version: V.4.5-2023.03.10.03

My bad onchange isnt triggered at all.
tried this. Onclick triggered only before value is changed. While i need to obtain new value before saving form.

[selector]

as a little workaround i tried to add

Code: Select all

$('#' + id + 'code').trigger('input');

in

Code: Select all

function nuGetLookupId(pk, id, setFocus, setEdited) 

There is a feeling that this is not right solution, but it works. I will be glad to hear an edit of this decision, which will be correct.

[kev1n]

I believe I haven't yet grasped the complete context of your objectives. Kindly provide a comprehensive, step-by-step explanation that includes the data entry process, the objects involved, the rationale for triggering the onchange event, the sequence of control interactions, and any other pertinent details. This will enable me to gain a clearer understanding of your goals and assist in devising the most suitable solution. Additionally, a screen recording demonstrating the process would be highly beneficial as well.