I have a form. Form has a dropdown list due to field being a lookup to "Client" Entity (Client Entity has 2 fields: ClientID, and ClientName. ClientID is the "Title" field)
The displaytext is the ID - how can I change the dropdownlist display text to be "ClientName", instead of the current "ClientID" ?
Solved! Go to Solution.
I have the following entities
I want to create an edit form for Client Contact, so I:
As above. I think this is a common/simple use case for related entities / lookups.
So what I want is:
Please select the card that contains your lookup field dropdown. Then on the right hand side pane under "Form Customization", spot your field, and click the "..." icon, and change the "Value" dropdown to ClientName. This will change the projection of that lookup field (which is a complex object in PowerApps) in the dropdown. The card will continue to see the entire complex field value underneath, but only the Client Name will be rendered.
I hope this helps.
Sorry for the insistence here, but I just want to make sure we are not missing something obvious.
I understand that the Value dropdown looks greyed out. However, styling side, are you sure it is disabled? Have you tried clicking on the dropdown to see if there are any other fields available?
Also, is Client Name a required field in the referenced list, or is it optional?
I have rechecked in the styling side, in the drop down, title alone is displayed. Also the ClientName is a required field in the refrenced list.
I have a Sql Server database with a couple hundred entities but I'm only interested in 50 or 60 at the moment. I have a need for 30 or 40 Lookups implemented with DropDown's which in the database are linked through foreign keys and 1:n reationships and I need a way to easily define these on a number of forms.
I have worked on LOB apps for 20 years across a range of industries and large companies and such a requirement is very, very common. In fact this requirement is on the small side so I am concerned with the earlier response describing 50 entities and 100 lookups as huge and complicated.
Such a response is indicative of PowerApps being designed only for tiny data models and therefore unsuitable for real LOB apps.
So, what's the deal with PowerApps - is it meant for real LOB apps or tiny demoware? Since the market and need for the former is huge I really hope that is where PowerApps is targeted...
Learn how to create your own user groups today!
Check out the new Power Platform Community Connections gallery!
Join us, in-person, December 7–9 in Las Vegas, for the largest gathering of the Microsoft community in the world.