[Feature]: Create a lookup control (for reference data)

[ciaomatteo]

**Is this request for a new component, or additional functionality for an existing component? **

Have you validated that your desired feature or component is not already in the backlog?

Describe the component and functionality you would like to see in the starter kit
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

[denise-msft]

@CrmDev23 thanks for sharing your feedback! Can you please share more details about the control you need? Is this a capability you want added into DetailsList, or is this an independent net new control? What information should this display, and is it specific to Dataverse LookUps or does SharePoint need to be supported? Or could you even be thinking of an office graph lookup?

[ciaomatteo]

@denise-msft: I was thinking of a component similar to a lookup field control in dataverse (model driven app), which provides search/autocomplete functionality. This is helpful when creating a custom page inside a model driven app, where the user must be able to reference and associate records from other entities to the current one (e.g. selecting a primary contact for an account).

[joergen78]

Totally agree with @CrmDev23 and was wondering what the suggested solution would be at the moment to have the same experience for lookup fields in a custom page, that is available in Model Driven Apps by default.
In addition to the above mentioned requirements,
I would add that the lookup component should have no Delegation issues - at least when adding a Dataverse table as source.

Nice to have features would be: The default lookup in Dataverse model driven apps also support some additional input options that would be great if these can be added in the configuration of a lookup component e.g. dependent lookup with filtering, maybe adding multiple tables as source to simulate multi-table lookups (owner or customer by default in Dataverse).