Hi,
I've setup an Query which will fetch data from the Get object manager instances and get the data from one definition. Then in that query I'll left join that table with another Get object manager instances to just to show the names instead of the guid of an DomInstanceFieldDescriptor field.
Now happens that in the table i show that field in the Column, what happens is that when i want to edit this entry i open the panel with the form and that form will show the joined instance instead of the first object instance.
The form has the correct definition loaded onto it but it still will change to the other defintion.
Hi Gerwin,
If I understand correctly, your joined query represents 2 DOM instances at the same time. In that case the form component will use the first instance that is fed as its input data. This is independent of the definition on the component. Definition data is used to create new instance, not to edit existing ones. The order the instances are fed from the table depends on the column order.
Since the joined instance is fed first, this makes me think that a column from the joined query is the first one in the resulting query? To make sure the correct instance is fed to the form component, you can use a select node & change the column order. Adding one of the initial query first, will feed the instance from that query fist.
Yes because the dom instance excist of two fields of other dom definitions and then multiple sections for an user lookup table.
I ran into this issue before because sometimes it makes more sense from an end user perspective to have the joined instance as first column in the table.
Also it would help if we can show the display value of an instance instead of the guid, then we dont have to to an lookup in the query.