Option B seems like the way to go. Creating a Screen Action to programmatically assign the widget to the data fetched by the Aggregate sounds like a good approach.
Hmm, I'm not entirely sure about this one. I'll go with option D and add an Expression inside the widget that refers to an attribute of the data fetched by the Aggregate.
I was a bit confused by this question, but I'm pretty sure the answer is C. The binding should be done automatically since the Aggregate is in the scope of the Screen.
I think the correct answer is option A. Setting the Source property of the widget to the output of the Aggregate is the easiest and most straightforward way to bind the data fetched by the Aggregate to a Table or List widget.
Brinda
1 months agoBecky
1 months agoYasuko
1 months agoVanna
3 days agoAja
8 days agoLavelle
18 days agoVashti
1 months agoAudra
14 days agoArlette
16 days agoMarion
16 days agoElza
17 days agoWilson
27 days agoEleni
1 months agoPearline
2 months agoElin
3 days agoSharmaine
4 days agoMignon
11 days agoAdell
12 days agoAriel
19 days agoLauran
25 days agoPaul
2 months agoHerschel
2 months agoRyan
2 months agoLai
2 months agoKris
2 months agoErin
3 months agoLeah
3 months ago