Three queries, one list report, and different values

[mrsbelley]

Hi there,

This is my first post (and my second month using Report Studio), so please be gentle. I tried searching for this topic in the forum, but couldn't find anything...though that could be because it's difficult to sum up in a few words.

My client wants to compare two different versions (aka time periods) of a project plan and the variance between the two; they want to see everything in a list report, but because of they way their data is set up, I need 3 different queries. I know enough to be able to cobble it together (with 2 identical queries, filtered on the version number and a union of those two), but the issue I'm running into is that Version 1 doesn't have as many entries as Version 2, so it doesn't match the other lists (thereby throwing off the alignment).

Is there some way to utilize the master-detail relationship to make this work? I spent a good deal of time today trying to link them in such a way that the separate lists all return the same information, regardless of whether there was a value for the given version. Ideally, both versions would pull back the same information as the Variance query.

Some details: this is relational data, and they want repeated staggered data - that doesn't make sense, but they essentially want values from the 3 queries repeated in a specific order through the list columns (see attached)

Any help at all would be greatly appreciated!!
mb

[PRIT AMRIT]

. I know enough to be able to cobble it together (with 2 identical queries, filtered on the version number and a union of those two), but the issue I'm running into is that Version 1 doesn't have as many entries as Version 2, so it doesn't match the other lists (thereby throwing off the alignment).

You may create dump entries(Data Items) in Version 1 Query and ensure the number of entries & datatype are similar for both Version 1 & Version 2. Then just UNION it. Should work for you.

[mrsbelley]

Thanks for the feedback, PRIT; however, I don't think I was clear enough in my initial post. I had already unioned the two version queries, and was getting results for all three. The problem was that the data being returned in the Version 1 query had fewer entries in the data itself (ie, Version 2 and the union query returned, for example, 20 item descriptions while Version 1 only returned 14).

I ended up asking the client to change the package to DMR and I was able to get the data to tie out correctly using one query instead of three.

mb