Can I add elements of different data types in a sing;e type group in ControlManifest.xml? @HemantG
I suspect you would be better off with multiple controls as you can only bind to one type at a time see https://docs.microsoft.com/en-us/powerapps/developer/component-framework/manifest-schema-reference/p...
This definitely works. I used it in one of my controls - https://github.com/AndrewButenko/CompositeAddress_PCF/blob/master/CompositeAddress/ControlManifest.I...
Here is an example:
<type-group name="StringOrOptionset"> <type>SingleLine.Text</type> <type>OptionSet</type> </type-group> <property name="state" display-name-key="State/Province" description-key="State/Province" of-type-group="StringOrOptionset" usage="bound" required="false" />
But which field type is bound to input you will have to analyze during runtime of the control.
Trust me to follow the out of date documentation.
Looking at my link it's a typo in list of types. Float is not an option it should be FP.
<type-group name = "MultipleTypes"> <type>SingleLine.Text</type> <type>SingleLine.URL</type> <type>SingleLine.TextArea</type> <type>Multiple</type> <type>Whole.None</type> <type>FP</type> </type-group>
HI @navneet_singh ,
Could you please share a bit more about your scenario?
Do you want to specify different data type within the <type-group> node, e.g. Whole.None and SingleLine.Text in same type group?
If you want to specify different data type within the <type-group> node, e.g. Whole.None and SingleLine.Text in same type group, I afraid that there would have some issue with it.
When you specified Whole.None and SingleLine.Text in same type group, they would not be considered as compatible types. The types considered compatible as below:
1. Strings: SingleLine.Text, Multiple, SingleLine.TextArea, SingleLine.Email, SingleLine.Phone, SingleLine.URL, SingleLine.Ticker. 2. Numbers: Decimal, Floating Point, Whole.None, Currency. 3. Dates: DateAndTime.DateAndTime, DateAndTime.DateOnly.
Please check the following article for more details:
If the types listed in the group are not considered compatible, then the parameter will be treated as the first type listed in the type-group.
Note: If you specified different data type within the <type-group> node, e.g. Whole.None and SingleLine.Text in same type group, there is no error with this configuration, but only the first type listed within this type group could be applied to current parameter.
Check out new user group experience and if you are a leader please create your group
Check out how to claim yours today!
Test your skills now with the Cloud Skill Challenge.