cancel
Showing results for 
Search instead for 
Did you mean: 

Crosstab with multiple rowset xml content

Former Member
0 Kudos

I have multiple rowsets (xml files) which I want to calculate subtotals from. Each xml data set has identical columns. If I union all the files together, the xml content contains multiple rowsets and the Crosstab function does not give me a summed value of each column, but instead it creates a column for each column in each rowset.

The Normalize and the rowset combiner transform both combine rowsets by appending the second dataset into new columns, is there any way to append the data into new rows instead?

Because my final file is going to have something over 30,000 rows (14Mb), I am reluctant to use a repeater on each row of each file to combine it into a new rowset. Is there an efficient way to handle this calculation?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

I used a solution proposed by Jeremy in another thread.

That is to use an XSL transform stylesheet to combine the rowsets. Jeremy was good enough to provide the code for the transform in the thread.

jcgood25
Active Contributor
0 Kudos

Sue - good to see you here on the forum and I'm glad to help, even if it was through osmosis

Regards,

Jeremy

Former Member
0 Kudos

Sam,

After I got the server rebooted, I tried using the JOIN again. After the 5th JOIN, Xacute began having memory errors, so I don't think this solution will work for me.

Runing the transaction with the transform only takes about half an hour and solves my problem.

0 Kudos

Sue,

Try using Join instead of Union.

-Sam

Former Member
0 Kudos

How can JOIN work? I want to append rows not columns.

0 Kudos

Sue,

Why don't you look at the documentation for the Join block and give it a try...then post a reply.

-Sam

Former Member
0 Kudos

According to the documentation the JOIN will not work for me.

When I tried it anyway, the server began thowing out of memory errors and corrupted the transaction.

0 Kudos

Sue,

I believe that we are off on the wrong foot here...all things aside...

Join will work for your scenario when combined with other actions for your calculation and it will be easier to maintain than a stylesheet which will be beneficial to you in the end. Please do not be too quick to judge the solution

As for the error message that's one for support, what was the error in the logs?

-Sam