Announcements
Hi Guys,
I have set-up combo boxes where if we enter a specific PO it pull all relevant information against the referenced PO. all of these combo boxes are connected to SQL database. Now the look-up work fine but I only see a very limited number of POs in the list and similarly a lot of POs do not look-up in the search but I can see them just fine when I look them up on SQL server.
Am I missing something is the data point limit to PowerApps ? Any possible work arounds to this ?
@Anonymous
I don't think there's enough information here to answer your question. Please show your code.
this is the code I am using for the PO look-up : Distinct('[sbi].[PurchaseOrders_History]','Purchasing Document Number').Result
Screenshot attached: now while the 658 PO is searchable and pops up in the combo box list. The 261 PO does not.
I am confused as to why the combox is unable to search or populate the complete list of POs. The same PO look-up just fine when I look it up through SQL server.
Thanks for your help!
Hi @Anonymous
The reason for this is because the Distinct function isn't delegable. There's more information here on this topic.
https://docs.microsoft.com/en-gb/powerapps/maker/canvas-apps/functions/function-distinct
With SQL Server, the workaround would be to create a SQL Server view that returns the distinct values, and to use that to populate your combobox.
Agreed with @timl. Suggest you take his advice.
---Please click "Accept as Solution" if my post answered your question so that others may find it more quickly. If you found this post helpful consider giving it a "Thumbs Up."
Thank you for your response, much appreciated it.
Can you please elaborate more on the work around, this actually the first tool that I am building and not sure where to go from here to have the complete data pull.
@timl I guide from Microsoft states that, there will be a delegation warning when the it may not be possible to do so, I do not see any warning on my application when I try to run it.
What can I do at this point to have a full pull from the SQL data source?
The workaround is to create a view like this in SQL Server..
CREATE VIEW [vwDistinct_PurchaseOrders] AS SELECT DISTINCT [Purchasing Document Number] FROM [sbi].[PurchaseOrders_History]
You would then add the view [vwDistinct_PurchaseOrders] as a data source to your app, and set the Items property of your combobox to this view. That should hopefully solve your problem.
@timl
Thank you so much, quick question here, I have other comboboxes that look-up values based on the PO number referenced, would those need a separate (distinct) SQL view to work in tandem with the PO view.
Thanks for your help. I will try it out and get back to you on whether it worked.
So long as you want to populate your other comboboxes with the same distinct values of POs, you can use the same view, rather than create separate views for each combobox.
I just implemented the SQL View this morning and will be testing out the solution later today, I will get back to you as soon as I have something on it ! thanks guys!
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.
Congratulations to our 2026 Super Users!
Congratulations to our 2025 community superstars!
These are the community rock stars!
Stay up to date on forum activity by subscribing.
Vish WR 839
Valantis 533
Haque 412
