web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Dropdown or Combo box ...
Power Apps
Suggested Answer

Dropdown or Combo box Library Component

(0) ShareShare
ReportReport
Posted on by 11 Season of Giving Solutions 2025
I've created a library component which has a dropdown but I can't figure out why it wont work in an app but works when testing in the component.
 
In the below example, we have a table myCollection.
{Value: "red", ID: 1}, {Value: "green", ID: 2}, {Value: "blue", ID: 3}
 
when testing, its possible to get a label to show componentDropdown.Selected.ID
However, when adding it to an app, only .Value will appear as a column you can select, no matter what the table.
 
 
Here is an example, Selected.ID should be present but it's not when the component is added to an app, but does appear when testing the component.
 
Has anyone managed to use a dropdown or combobox in a library component where you can manipulate the searchfield or displayfield? Or even get them to pass more than a single "Value" column?
Screenshot 2025-12-02 103900.png
Screenshot 2025-12-02 103932.png
Categories:
I have the same question (0)
  • Suggested answer
    Michael E. Gernaey Profile Picture
    53,960 Moderator on at
     
    This is pretty common and standard, its actually (now adays another issue even internally when you bind to even SharePoint where in the collection it doesn't add the ID by default)
     
    Anyway, I digress. If you want the ID, you will have to create an output property to expose it, or you can also create an output property the exposes the entire Collection and then bind that to the Control. I know it sounds stupid, but the issue is it does not expose it by default because there is no schema outside of the Control and Value is always there.
     
    Think of it like the Component Inputs, you have to define the schema so the Component knows what is coming in, same for the Outputs, your app has no way to know what the schema is because only the Component does.
     
    Unless of course you turn on App Access and just use a global Collection as an input which defeats the purpose.
     

    If these suggestions help resolve your issue, Please consider Marking the answer as such and also maybe a like.

    Thank you!
    Sincerely, Michael Gernaey
  • SFRSDL Profile Picture
    11 Season of Giving Solutions 2025 on at
     
    How would you resolve this then?
     
    The collection in my example is being created within the app, not just held within the components items property.
    I have an input on the component, called "Items" (type: Table) and the dropdown inside the component has its "Items" property pointing to this.  E.g "componentDropdown.Items"
    I also then have an output (type: Record) for both Dropdown1.Selected and Dropdown1.SelectedText 
     
    Here is the YAML
     
    ComponentDefinitions:
      Component1:
        DefinitionType: CanvasComponent
        AllowCustomization: true
        CustomProperties:
          Items:
            PropertyKind: Input
            DisplayName: Items
            Description: The Items that are held in Dropdown1
            RaiseOnReset: true
            DataType: Table
            Default: =
          RecordSelected:
            PropertyKind: Output
            DisplayName: Record-Selected
            Description: Dropdown1.Selected
            DataType: Record
          RecordSelectedText:
            PropertyKind: Output
            DisplayName: Record-SelectedText
            Description: Dropdown1.SelectedText
            DataType: Record
        Properties:
          RecordSelected: =Dropdown1.Selected
          RecordSelectedText: =Dropdown1.SelectedText
        Children:
          - Dropdown1:
              Control: Classic/DropDown@2.3.1
              Properties:
                Items: =Component1.Items
                Items.Value: =Value
     

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 549 Most Valuable Professional

#2
Kalathiya Profile Picture

Kalathiya 225 Super User 2026 Season 1

#3
Haque Profile Picture

Haque 224

Last 30 days Overall leaderboard