Property tag working different for field and dataset control

(0) Share

Report

Posted on by Sheldon Copper

200

Hi,

We are working on a dataset control and came across a situation where we wanted to get additional entity fields data apart from which we are getting from Views, so we used property-set but as of now property-set doesn’t support Lookup, Multiset Option set, and few other types fields.

In order to handle this, we can use the addColumn method in the code and get the values for it.

However, our issues are that the property-set (usage=input) now only allows us to type the field value, the dropdown is greyed out. But, I remember this being not the case initially and surprisingly it works for field control and we can either enter a hardcoded value or select field we wanted the same thing to work on dataset control.

We also tried using the property tag, but, the output is the same.

You can find attached the controlmanifest.xml for our control.

Please suggest if we are doing something wrong.

Thanks!

Sheldon

ControlManifest.docx

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (3)

Answers (0)

Sheldon Copper 200 on at

Like (0)

Report
Copy link

Link copied!

I am missing something??

Please help @jopursle @v-monli-msft @v-xida-msft @AnqiChen

Thanks,
Sheldon

Was this reply helpful? Yes No
AnqiChen Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

hi sheldon,

Your understanding is correct.

For data-set control, the 'property-set' is 'bound' only. And all candidate fields are from the <data-set> node associated entity.

The 'property' node, sibling of <data-set> node is for static input only.

Now the issue is that the 'property-set' does not allow you to pick all available attributes. For example, lookup & multi-optionset are not in the candidate.

Per my understanding, the multi-optionset might still yet to be exposed. But simply for 'lookup', a quick work-around (we have not fully expose, but u could try) is:

1) For the node_module, 'pcf-scripts'

2) Find the file, 'ManifestSchema.json' and edit it

3) with the 'dataType' list, add "Lookup.Simple" in the 'enum'

And after that, u should be able to unblock lookup in the property-set and use 'Lookup.Simple' as the type.

We have not yet expose the 'lookup', but if u just put it for <property-set>, it should be fine.

Was this reply helpful? Yes No
Community Power Pla... Microsoft Employee on at

Like (1)

Report
Copy link

Link copied!

Hi All,

In the latest version of PCF control project template above workaround does not work anymore due to some changes in the validation configuration. However, it is still possible.
Find and open this file in the project tree node_modules/pcf-scripts/featureflags.json
Then all you need to do is to set "pcfAllowLookup" to "on" and re-build the project.

Hope this helps 🙂

Was this reply helpful? Yes No