Skip to main content

Notifications

Community site session details

Community site session details

Session Id :
Power Apps - Power Apps Pro Dev & ISV
Unanswered

Lookup input with dataset control.

(0) ShareShare
ReportReport
Posted on by 480

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?

  • skoofy5 Profile Picture
    480 on at
    Re: Lookup input with dataset control.

    If you look earlier in this thread you will see my workaround.

     

  • Community Power Platform Member Profile Picture
    on at
    Re: Lookup input with dataset control.

    Is this bug fixed or anyone have any approach which can help here, since I am also facing the same issue with my grid control. I need 3 lookup inputs for performing some operation on grid command buttons, but the grid stops rendering on setting values of the lookups.

     

  • skoofy5 Profile Picture
    480 on at
    Re: Lookup input with dataset control.

    It's just a control that sits on a lookup and allows you to embed a form from that related entity.

    https://docs.microsoft.com/en-us/powerapps/maker/model-driven-apps/form-component-control

  • Polmon Profile Picture
    21 on at
    Re: Lookup input with dataset control.

    It seemed to be picking up the changed value when the underlying field changed even when it was usage="input". I would want to retest this to confirm, but I'm sure that was how it was behaving (that's definitely the way it is behaving for my Lookup PCF which has a different lookup field as an input property).

     

    I've not heard of Form Component Controls; are they new / preview?

  • skoofy5 Profile Picture
    480 on at
    Re: Lookup input with dataset control.

    Would it pick up the current value if it's just an input and not bound? I thought it would just load the once.

    For this reason I had actually investigated the "Form Component Control". 

  • Polmon Profile Picture
    21 on at
    Re: Lookup input with dataset control.

    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.

  • skoofy5 Profile Picture
    480 on at
    Re: Lookup input with dataset control.

    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;
  • Polmon Profile Picture
    21 on at
    Re: Lookup input with dataset control.

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

  • skoofy5 Profile Picture
    480 on at
    Re: Lookup input with dataset control.

    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 node declares whether this 3rd party PCF control is using external service or not, if yes, this control will be considered as premium and please also add the external domain it is using.
     If it is not using any external service, please set the enabled="false" and DO NOT add any domain below. The "enabled" will be false by default.
     Example1:
     <external-service-usage enabled="true">
     <domain>www.Microsoft.com</domain>
     </external-service-usage>
     Example2:
     <external-service-usage enabled="false">
     </external-service-usage>
     -->
     <external-service-usage enabled="false">
     <!--UNCOMMENT TO ADD EXTERNAL DOMAINS
     <domain></domain>
     <domain></domain>
     -->
     </external-service-usage>
     <!-- dataset node represents a set of entity records on CDS; allow more than one datasets -->
     <data-set name="sampleDataSet" display-name-key="Dataset_Display_Key">
     <!-- 'property-set' node represents a unique, configurable property that each record in the dataset must provide. -->
     <!-- UNCOMMENT TO ADD PROPERTY-SET NODE
     <property-set name="samplePropertySet" display-name-key="Property_Display_Key" description-key="Property_Desc_Key" of-type="SingleLine.Text" usage="bound" required="true" />
     -->
     </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"/>
     <!-- UNCOMMENT TO ADD MORE RESOURCES
     <css path="css/minHeightDatasetTEST.css" order="1" />
     <resx path="strings/minHeightDatasetTEST.1033.resx" version="1.0.0" />
     -->
     </resources>
     <!-- UNCOMMENT TO ENABLE THE SPECIFIED API
     <feature-usage>
     <uses-feature name="Device.captureAudio" required="true" />
     <uses-feature name="Device.captureImage" required="true" />
     <uses-feature name="Device.captureVideo" required="true" />
     <uses-feature name="Device.getBarcodeValue" required="true" />
     <uses-feature name="Device.getCurrentPosition" required="true" />
     <uses-feature name="Device.pickFile" required="true" />
     <uses-feature name="Utility" required="true" />
     <uses-feature name="WebAPI" required="true" />
     </feature-usage>
     -->
     </control>
    </manifest>
  • Diana Birkelbach Profile Picture
    3,072 Most Valuable Professional on at
    Re: Lookup input with dataset control.

    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?

     

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Announcing the Engage with the Community forum!

This forum is your space to connect, share, and grow!

🌸 Community Spring Festival 2025 Challenge Winners! 🌸

Congratulations to all our community participants!

Warren Belz – Community Spotlight

We are honored to recognize Warren Belz as our May 2025 Community…

Leaderboard > Power Apps - Power Apps Pro Dev & ISV

#1
WarrenBelz Profile Picture

WarrenBelz 107 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 72 Super User 2025 Season 1

#3
mmbr1606 Profile Picture

mmbr1606 71 Super User 2025 Season 1

Overall leaderboard