{"id":3405,"date":"2023-04-12T15:32:59","date_gmt":"2023-04-12T15:32:59","guid":{"rendered":"https:\/\/quebit.com\/askquebit\/quebit-standard-turbointegrator-process-cleanup-subsets-and-views\/"},"modified":"2026-01-16T16:49:19","modified_gmt":"2026-01-16T16:49:19","slug":"quebit-standard-turbointegrator-process-cleanup-subsets-and-views","status":"publish","type":"post","link":"https:\/\/quebit.com\/askquebit\/quebit-standard-turbointegrator-process-cleanup-subsets-and-views\/","title":{"rendered":"How Do I Use the QueBIT Standard TurboIntegrator Process to Clean Up Data, Manage Subsets, and Create Views?"},"content":{"rendered":"

QueBIT standard TurboIntegrator (TI) processes are used on IBM Planning Analytics (powered by TM1) implementation projects to accelerate the development process and reduce implementation costs. They are included at no charge to QueBIT clients.<\/p>\n

This note documents the QueBIT \u2013 Cleanup Subsets and Views<\/em><\/strong> TI process. Click here<\/strong><\/a> to download it.<\/p>\n

Functional Description<\/span><\/h3>\n

This TI process will delete all PUBLIC views and subsets for all cubes and dimensions in a single TM1 server application, whose names contain a substring that the user specifies.<\/p>\n

After it is run, files with .vue<\/em><\/strong> and .sub<\/em><\/strong> extensions stored in folders with }vues<\/em><\/strong> and }subs<\/em><\/strong> suffixes under the TM1 server application data directory on the server will be erased.<\/p>\n

PRIVATE views and subsets are not affected.<\/p>\n

WARNING<\/strong>: Use this TI process with care. Once a cube view or subset object is removed, it can only be restored from a backup. We recommend ensuring that you have a good backup copy available to you in the event you erase an object you did not mean to erase.<\/p>\n

Use Case 1:<\/strong><\/span><\/p>\n

TI processes sometimes assemble cube views and subsets on the fly, to use as data sources for batch operations, or as target areas to be cleared (using the VIEWZEROOUT<\/a> function).<\/p>\n

While it is good practice for any TI process that creates a temporary view or subset object to destroy them when it is complete, sometimes the process may be interrupted before the clean up step has taken place. Other times, a developer may choose not to destroy these objects while doing development to maintain an audit trail of what is going on, with the intention of cleaning up later.<\/p>\n

Regardless, these subset and view objects can accumulate over time.<\/p>\n

Use Case 2:<\/strong><\/span><\/p>\n

Modelers and other administrative users (who are the only users able to create PUBLIC subsets and views) often create cube views and subsets as they explore the data. Sometimes these are created as part of an ad-hoc analysis that is important for a day or two, but not in the long run.<\/p>\n

These subset and view objects can also accumulate over time.<\/p>\n

Example:<\/strong><\/span><\/p>\n

In this example we are looking at an application that includes a cube named Sales Commissions Assumptions<\/em><\/strong>, which has a dimension of the same name. The cube has a PUBLIC cube view named 1tmp_view<\/em><\/strong>, and the dimension has a public subset named 1tmp_subset<\/em><\/strong>.<\/p>\n

\"\"<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

You may not have access to the Database Directory for the application on the TM1 server, but if you do, you will see files with these names in the }subs<\/em><\/strong> and }vues<\/em><\/strong> folders prefixed with the name of the dimension or cube:<\/p>\n

\"\"<\/p>\n

 <\/p>\n

Run the TI process with these parameters:<\/p>\n