Currently, it is not possible to define a property for attribute type Lookup.
Please add support for this type
Marking this idea as complete - https://aka.ms/PCFBLog with the recent release we added support for Simple lookup and MSOS (Multi select option set)
Lookup has complex set of APIs to function in full capacity and we are evaluating if we can release the support in staged manner. This workitem is under review currently.
I do understand that some type of attributes can be harder to integrate (especially regarding Canvas app), but I really think all data type from CDS should be supported
Currently planned for the next semester (April 2020) - please note that actual delivery dates can change .
Will this be in the new Aril 2020 release? @HemantG
I couldn't find any further information regarding this change.
This didnt make it to April release but I am trying to prioritize this for next one.
@HemantG, is this about binding a lookup field to a property of a PCF control, or about binding a PCF control to a lookup field, or both?
@HemantG checking in on this, whats the likely timeframe for this to be released?
@HemantG thanks for prioritizing this important feature. Let us know if it will be in 2020 Wave 2@EvertJanvdBosch someone correct me if I'm wrong, but this is related to binding a PCF control to a lookup field. Lookup controls are not supported when defining types in the type group in the control manifest: https://docs.microsoft.com/en-us/powerapps/developer/component-framework/manifest-schema-reference/t...
Some movement, looks Lookup properties have been added to the Control Manifest in the latest release of pcf-scripts - https://www.npmjs.com/package/pcf-scripts/v/1.3.6
@HemantG Any news on this one?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.