[Bug]: Display field issue on custom relationship with a Virtual table

[djidji33]

Component

PolyLookup

Component version

1.1.1.0

Current Behavior

After having configuring the following relation:
Registration (Standard) - 1n -
Registration_Item (Standard) - n1 -
Catalog Item (Virtual)

I have an issue with the polylookup, on the creation of a record we can see all the fields (of course it is unusable at this stage):

After creating the record, we can add items in the Polylookup but all the display items are empty and we can select multiple times the same element:

However the relation is correctly implemented, it seems it's just about getting the data in the Polylookup to be displayed:

It would be very helpful for me if it was possible to find a corrective for this, with the fact that many-to-many relationship is not available with virtual table so custom relationship is the only way.

Thank your for your great work!

Best regards,
Djilali

Expected Behavior

We should be able to display the content of the selected element, and thus prevent the multiple selection of the same item (if possible)

Steps to reproduce

1. Create one Standard table (1)
2. Create one Virtual table (2) with a primary key "id" with Int type
3. Create one Standard table (3) to link thos two table for many-to-many relationship
4. Add a Polylookup on the Standard table (1) and link the two tables

Additional context

No response

[khoait]

hi, thanks for reporting. this is interesting with Virtual table. looks like the component cannot retrieve display name from the virtual record. my guess is that there is no actual relationship table 3 and table 2, so the link-entity in fetch doesn't work normally. I'll look into this.

[Reitangle]

I'm experiencing the same issue, using a custom n:n relationship to the Entra ID Users (virtual) table.

PolyLookup version: 1.1.2.0

Configuration:

Relationship Type: Custom N:1-1:N (value 1)
Relationship Name: prefix_orgfunction_1n_orgfunctionaaduser (1:N from host to intersect)
Relationship 2 Name: prefix_orgfunctionaaduser_n1_aaduser (N:1 from intersect to aaduser)
Intersect entity primary name field: prefix_name
Target entity: aaduser (Dataverse virtual entity for Azure AD users).

Behaviour:
The control renders correctly
The dropdown search works and returns aaduser records as expected following the aaduser table's lookup view
Selecting users creates intersect (prefix_orgfunctionaaduser) records correctly
Selected tags appear as empty - no display text