Metadata configuration parameters in PCF control

[d365clubnet]

Hi,

I'm looking for information on how to provide control parameter so I could point entity from list of entities in one and a view or an attribute of that entity in the other param.

Something similar to what MS did on Auto Complete Control for selection Entity, View, field within selected view to provide picklist values over text field.

Cheers,
Eryk

[ben-thompson]

You may wish to look at my Meta Data select PCF components that allow you to do just that. They are all separate controls, so start with select entity to chose an entity and then pick the appropriate control for whatever you wish to do next (select view, select attribute)...

The solutions include managed, unmanaged and source code can be found at https://github.com/bthompson-365/PCF-Metadata

[ScottDurow · Accepted solution]

Perhaps @d365clubnet  you are asking about the control parameters that are passed to the control at design time? If so - there isn't any way currently to customise this experience - you basically have a bound or input (static) value that you can provide - no additional UI logic.

[d365clubnet]

@ben-thompson Thank you for your response. This is however more about control configuration parameters.

Cheers,

Eryk

[d365clubnet]

Hi @ScottDurow ,

This is exactly what I meant. MS autocomplete shows this is possible (not necessary supported as of now) just I wondered if any kind of api exists for that.

Cheers,
Eryk

[PowerMaverick]

@d365clubnet 

You could do a bound field and apply logic on the data in that field which can drive your custom control.

*If you can describe your exact scenario maybe there might be a better way to implementing it. 

----
Danish Naglekar | Power Maverick
If this post helps, then please consider Accept it as the solution to help the other members.

[ben-thompson]

The other way of doing that would be an configuration entity / environment variable that the PCF component called to retrieve the appropriate configuration.

Yes it's not the neatest approach but I find configuration entities can make things non-code friendly in a way that other things don't.