Unanswered

Gallery in component breaks delegation

(1) Share

Report

Posted on by Tricky

Hi All,

I'm working through an existing app to allow delegation for any lists of information (So we don't hit the 2000 non-delegable limit) but have hit a small but important problem.

If I have a gallery view (used to list out information) inside a custom component (either a custom component inside the app or, a component held within a separate component library which I include in my app) that gallery is limited to only showing the total number of items allowed by the non-delegable limit set in my app settings (in this case I have it set to 1 to test).

I have another gallery view on the same screen of the same app using the same logic to retrieve content from the same connection and it works as expected (returning all the results expected not just the 1 limited by my app settings).

I hope this makes sense and wonder if anyone has experienced the same?

Hoping someone might be able to provide a little insight.

Categories:

Building Power Apps

All responses (9)

Answers (0)

Sort by

WarrenBelz 156,736 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

@Tricky ,

The Delegation limit will apply only to non-delegable queries. If your second query is Delegable, it will work as expected.

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.
Tricky 35 on at

Like
a
(1)

Report
Copy link

Link copied!

@WarrenBelz

That's what I thought too, but when you place the delegable query into the input (custom property) of a component it stops delegation completely.

I just tested it with a completely clean direct SQL DB reference (e.g. '[dbo].[something]') with no other filters/searches etc. applied.

Gallery inserted directly into the screen with input set to DB/connection ref - works as expected
Gallery inside (app local) component connected via custom property called "Items" (set to 'table' type) - returns a single entry
Gallery inside (component library) component connected via custom property called "Items" (set to 'table' type) - returns a single entry

All of the above based on my "Data row limit for non-delegable queries" set to 1.

If I set the value to 3, In screen gallery works as expected returning all items and component based galleries only return 3.
WarrenBelz 156,736 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

@Tricky ,

I do not use components presently, so cannot comment, however the behavior outside them seems usual.

Are you saying that Delegable queries still take only the limit?

I will tag a couple of my colleagues here @mdevaney and @RandyHayes for their thoughts.
Tricky 35 on at

Like
a
(0)

Report
Copy link

Link copied!

Yes, my delegable query is being limited (to the max value set for non-delegable queries), but only when the gallery I am using to display the data is inside a component. Galleries that exist on the screen directly work as expected.
Tricky 35 on at

Like
a
(0)

Report
Copy link

Link copied!

@WarrenBelz Does it make sense to raise this as a potential bug?

I'm struggling to find any information to confirm that what I'm experiencing is the expected result and the documentation at (https://docs.microsoft.com/en-us/powerapps/maker/canvas-apps/delegation-overview) doesn't mention this usage case as being a potential issue.

Would greatly appreciate any more input/information as this is going to cause issues with the ability to use components as a way to allow more developers to work on the same project at the same time.

Thanks in advance
WarrenBelz 156,736 Most Valuable Professional on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @Tricky ,

It could be a bug - I will try another couple of my colleagues @Anonymous and @PowerAddict
Community Power Pla... Microsoft Employee on at

Like
a
(0)

Report
Copy link

Link copied!

@WarrenBelz @Tricky

I think I read on these forums (somewhere?) that this is a known issue with components. Like Warren, I don't use components simply because they are still experimental/In Preview and not recommended for production apps - at least that's my understanding.

Maybe trying searching on Google and/or in these forums for a post that talks about these issues?

Sorry I couldn't be more help
pvpatrick 23 on at

Like
a
(0)

Report
Copy link

Link copied!

@Tricky Did you ever get this resolved? I am running into the same issue and have spent hours trying to figure out why a delegable query wasn't working inside my component until I cam across this thread. Extremely frustrating.
Tricky 35 on at

Like
a
(1)

Report
Copy link

Link copied!

@pvpatrick. Sadly not, eventually built a workaround to collate all of the results I wanted into a collection, then passing the collection into the component for display. There are a couple of ways to do that depending on your particular situation so it may be worth describing what you're trying to do, here.