Unanswered

Lookup input with dataset control.

(0) Share

Report

Posted on by skoofy5

482

I'm making a dataset control that will sit on a form. I'm also trying to pull in additional data if it exists from a lookup control, but when I add it and hook it up to a value on the form the dataset stops loading.

<property name="lookupField" display-name-key="lookupField" description-key="lookupField" of-type="Lookup.Simple" usage="input" />

That's all I've done and when I configure it with a value the control dataset stops loading. Is this not allowed?

Categories:

Power Apps Pro Dev & ISV

I have the same question (0)

All responses (15)

Answers (0)

cchannon 4,702 Moderator on at

Like (0)

Report

I haven't tried using a lookup as an input and not as bound, but I wouldn't be surprised if that is the issue: that a lookup can only be bound, not input.

Was this reply helpful? Yes No
skoofy5 482 on at

Like (0)

Report

Why not surprised? Is there a technical reason?

Thanks for helping my understanding.

Was this reply helpful? Yes No
cchannon 4,702 Moderator on at

Like (0)

Report

Because it would be pretty much impossible for you to provide a static value for a lookup. It would only be practical to provide a field reference.

Just a guess.

@DianaBirkelbach do you know? Is it possible to have lookup.simple as usage input and not bound?

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like (0)

Report

Hi @skoofy5 , Hi @cchannon ,

In my opinion it should work, and if it doesn't, it might be a bug.

Could you share the manifest with us?

BUT, I would ask if the lookup of type input would help much? Having it only of type "input" on a model-driven app form means, that you get the value only the first time the PCF is loaded, but you don't get the value in case the lookup changes on the form. The user would need to refresh the form. Would that be enough for your use-case?

What actually means "the control dataset stops working"? Do you see an error in the console? Are you still able to attach the PCF to a (another) dataset (is it still in the list of available PCFs for the dataset)?

Let's see if we find a solution together...

Was this reply helpful? Yes No
skoofy5 482 on at

Like (0)

Report

I can force the form to reload if I need the updated value - which should be pretty rare so input is fine. It doesn't throw an error, the dataset parameter just returns an object with empty values when I add the property as above to my manifest AND configure it (i.e. assign a field to it on the form). This seems to happen with a default manifest.

Was this reply helpful? Yes No
Diana Birkelbach 3,072 Most Valuable Professional on at

Like (0)

Report

Hi @skoofy5 ,

Sounds like a bug. Would be good to confirm that the issue doesn't happend when it's a string property (but I think you would need to remove the PCF before you change the property type).

What do you mean by "default manifest"?

@HemantG : Is this a know issue?

Was this reply helpful? Yes No
skoofy5 482 on at

Like (0)

Report
Default as in what's generated.

<?xml version="1.0" encoding="utf-8" ?> <manifest> <control namespace="datasetControl" constructor="datasetControl" version="0.0.1" display-name-key="datasetControl" description-key="datasetControl description" control-type="standard" >  <external-service-usage enabled="false">  </external-service-usage>  <data-set name="sampleDataSet" display-name-key="Dataset_Display_Key">   </data-set> <property name="lookupField" display-name-key="lookupField" description-key="lookupField" of-type="Lookup.Simple" usage="input" /> <resources> <code path="index.ts" order="1"/>  </resources>  </control> </manifest>

Was this reply helpful? Yes No
Polmon 21 on at

Like (0)

Report

Is there any update on this issue? I've encountered the same problem with my dataset control with a lookup field as an input.

Was this reply helpful? Yes No
skoofy5 482 on at

Like (1)

Report
I've not heard anything about a fix.

I ended up writing my own query by grabbing the current form id/etn and added a text param property where I would set the schema name of the lookup.
const entityId = (context.mode as any).contextInfo.entityId; const entityTypeName = (context.mode as any).contextInfo.entityTypeName; const lookupField = context.parameters.lookupSchemaName.raw;

Was this reply helpful? Yes No
Polmon 21 on at

Like (0)

Report

Thanks @skoofy5, that's the same thing I ended up doing. Its not ideal as it only picks up the saved value, not whatever is currently selected in the control, but it's enough to get it working for now. Hopefully we will get a fix for this sometime soon.

Was this reply helpful? Yes No