Variable Sets messing with report?

[davidvetter]

Hi all. Not sure how to find a solution to this problem...

I have 5 unique catalog items for requesting provisioning services broken into t-shirt sizes XS, S, M, L, and XL.

Each catalog item has its own variable set, but each variable set contains the same variables.

When building a dashboard widget for a report to show open and closed RITMs from those catalog items the report looks similar to this:

RITM#   SO#   ASP   Environment    RITM#   SO#   ASP   Environment    RITM#   SO#   ASP   Environment

100        111    abc    xyz

101        112    def     xyz

102        113    abc     xyz

                                                             103        114    def    xyz

                                                             104        115    ghi    xyz

                                                                                                                          105        116   abc     xyz

....instead of one singular list of "RITM#   SO#   ASP   Environment" for all of them.

The report in the widget looked fine up until RITM# 102. At that point, I pushed an update set that adjusted the catalog items to add catalog client scripts for some customization. Then again an update set at RITM# 105.

The only glaring factor I see causing this (besides the update sets) is the fact that 103 and 104 are XS size items, and 105 is a Small. Could the variable sets for the items (because they contain the same variables, just unique to the variable set for an XS, S, etc) be causing this? Bear in mind that RITM# 100 was a Medium. 101 and 102 were XS...so the sudden shift at 103 to a totally new column grouping is hurting my head.

[Mark Manders]

Can you please explain why you are using 5 variable sets, containing the same variables? There is only one reason variable sets exist and that is for reusing them on items that need the same information. Just put the same variable set on all catalog items and your issue is resolved, because you will be reporting on the same variables (which all have their own sysids).

[davidvetter]

Using 5 because there is example text for certain fields that varies depending on the t-shirt size. 

[Mark Manders]

Just put a general explanation in there. The t-shirt size example text shouldn't be the reason to have 5 variable sets. 

[davidvetter]

"general explanation" isn't sufficient. I have 5 fields that need require a number to be entered and the max number for each field varies by the t-shirt size. This is a new process for users and they need a reference.