In a standard database, each field of a row contains a single value. This is not the case for BO CMS database. A property can have a quite complex structure. A simple example is SI_DSL_UNIVERSE property for Web Intelligence documents that indicate what Unx universes are used by the document.
SELECT si_name, si_universe, si_dsl_universe FROM ci_infoobjects WHERE si_kind = 'Webi' AND si_instance = 0 AND si_name = 'Customer Profitability Comparison, by Customer'
The result in the SAP BO Query Builder will look like:
Exporting metadata for such object using “Include containers” in Biclever CMS Query Builder will create a single row and the fields for the property will be SI_DSL_UNIVERSE.1, SI_DSL_UNIVERSE.2, SI_DSL_UNIVERSE.3, SI_DSL_UNIVERSE.SI_TOTAL
The wide format is sometimes inconvenient. “Transpose” will create a row for each value of each array.
Thanks, was wondering exactly what it was for.
Your CMS query builder tool is helping me immensely in a migration from 4.1 SP7 to 4.2 SP4 by allowing me to identify all the schedules in the old system and provide that to the end users to determine what I can clean up as part of the upgrade.
Thanks heaps for your effort, it’s really appreciated!
Cheers,
Sam
The transpose option is great… any chance you could support it in the cmsquery-cmd program ?