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
13 days agoBecky
15 days agoYasuko
16 days agoVashti
24 days agoWilson
9 days agoEleni
16 days agoPearline
1 months agoAriel
1 days agoLauran
7 days agoPaul
29 days agoHerschel
2 months agoRyan
2 months agoLai
2 months agoKris
2 months agoErin
2 months agoLeah
2 months ago