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

Notifications

Announcements

Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Power Apps / Cascading Dropdowns De...
Power Apps
Unanswered

Cascading Dropdowns Delegation Warning

(0) ShareShare
ReportReport
Posted on by

I have a Power App that connects to a SharePoint list with over 3000 items to choose from in a cascade of dropdowns in a power app.  One of the fields in SharePoint is a calculated field named Location that concatenates ID, City, and Address.   In the app there are dropdowns and one combo box that cascade.  The first Dropdown is Region, and then the second field in the cascade is the combo box that looks up the calculated field called Location whose parent is region.  This part works fine and pulls up the 'Locations' in the chosen Region(no delegation warning).  The next cascading dropdowns are ID, City, Address.  I simply want to fill ID, City, and Address in automatically based on what was chosen in Location as each choice in Location is distinct.  It works for most of the records but not all of them, and it must be because I'm getting a delegation warning.  Here is the formula in the City field items:  Distinct(Filter(OpenStores, Location = LocationCB.Selected.Value),City). The other fields have a similar formula. After Region is selected, it limits the Locations to only a few hundred, so it's not making sense.    How can I update to always make the ID, City, and Address populate?  

PowerApp.png

 

 

Categories:
I have the same question (0)
  • WarrenBelz Profile Picture
    153,034 Most Valuable Professional on at

    Hi @theBrianL ,

    You can improve the Delegation capability like this as Distinct() is not Delegable

    With(
     {
     _Data:
     Filter(
     OpenStores, 
     Location = LocationCB.Selected.Value
     )
     },
     Distinct(_Data,City)
    )

    and this will work providing the output of the top filter is under your Delegation limit. However there is one concern I have here - you mentioned something about a calculated column - if Location is a SharePoint calculated column, they simply do not work consistently with Power Apps, are not Delegable and should be avoided.

     

    Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

    MVP (Business Applications)   Visit my blog Practical Power Apps

     

     

     

  • theBrianL Profile Picture
    on at

    I put that formula in, and I still show the delegation warning. It also behaves the same way in that some of the locations I select don't populate the City.  The top level for Region is Distinct(OpenStores,Title).  Should that be changed as well?  

  • theBrianL Profile Picture
    on at

    The ones where it doesn't populate are after I select region and then on Location, I scroll down toward the bottom of the filtered Location list.  The bottom 15 or so won't populate the city like it does on all the other ones.  

  • WarrenBelz Profile Picture
    153,034 Most Valuable Professional on at

    @theBrianL ,

    Firstly, can you please clarify your comment that looks up the calculated field called Location - what type of field is this in your SharePoint list ?

  • theBrianL Profile Picture
    on at

    I figured out it only doesn't work when it goes past the 2000 row in the list.  There are 2183 records it pulls from.  The location field is a calculated field that concatenates the city, address, etc.  I'm not sure a way around this, because I would like for users to search on this combo box field, as they might not know the address, but at least they could search the city and it would pull up all the locations under city.  So they end up selecting a field like 15(Location ID) Rochester, 123 Main St.  Then after they select this the City Populates in the city field, address in the address field etc.  

  • Verified answer
    WarrenBelz Profile Picture
    153,034 Most Valuable Professional on at

    @theBrianL ,

    That was what I suspected - SharePoint Calculated columns do not "play well" with Power Apps as it was never really designed with this historic SharePoint column type in mind and they are totally not Delegable. You could use AddColumns in Power Apps (more reliable but still not Delegable). To be honest my approach would be to have a Location Text field and populate it with this combined data when a record is created. 

     

    Please click Accept as solution if my post helped you solve your issue. This will help others find it more readily. It also closes the item. If the content was useful in other ways, please consider giving it Thumbs Up.

    MVP (Business Applications)   Visit my blog Practical Power Apps

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

Forum hierarchy changes are complete!

In our never-ending quest to improve we are simplifying the forum hierarchy…

Ajay Kumar Gannamaneni – Community Spotlight

We are honored to recognize Ajay Kumar Gannamaneni as our Community Spotlight for December…

Leaderboard > Power Apps

#1
WarrenBelz Profile Picture

WarrenBelz 717 Most Valuable Professional

#2
Michael E. Gernaey Profile Picture

Michael E. Gernaey 329 Super User 2025 Season 2

#3
Power Platform 1919 Profile Picture

Power Platform 1919 268

Last 30 days Overall leaderboard