|
Re: Column Mapping from one node name to multiple fields [message #554949 is a reply to message #554911] |
Tue, 24 August 2010 20:49 |
|
Nick,
Why not use score as the row and then add score as column and name as
column. You could do a different dataset for the person row and then
nest the tables if you needed to.
Jason
On 8/24/2010 1:12 PM, Nick P. wrote:
> <root><person identifier="123">
> <score name="ACT">22</score>
> <score name="SAT">1400</score>
> <score name="AP Chemistry">4</score>
> </person>...</root>
|
|
|
|
Re: Column Mapping from one node name to multiple fields [message #554959 is a reply to message #554953] |
Tue, 24 August 2010 22:07 |
|
You could use a dataset parameter on the score dataset, but if that is
to complex for the users, you could always, put a list in for person
dataset and then nest score dataset table/list. On that table you could
just add a filter based on the outer table/list person.
Jason
On 8/24/2010 5:30 PM, Nick P. wrote:
> Jason,
>
> I have looked at that and had not yet ruled it out.
>
> I was concerned that it would not be possible to have multiple data sets
> overlapping in the layout. If we had a list that was tied to the person
> data set would it be trivial to drag in elements from the score data set
> and drop them into the list that is bound to the person data set?
>
> I think I see how this could be done but I worried that they might not
> be attached to the appropriate person.
|
|
|
Powered by
FUDForum. Page generated in 0.02893 seconds