Clarity: The Slice Tables for a user-defined TSV are empty

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Description:

When a TSV attribute is created, the application automatically creates slice request definitions for 4 tables: ODF_SL_nnnnnnn, ODF_SL_nnnnnnn_D, ODF_SL_nnnnnnn_W, ODF_SL_nnnnnnn_M
In the PRJ_BLB_SLICEREQUESTS table, the IS_ACTIVE field = 1 for the default ODF_SL_nnnnnnn table.
However the IS_ACTIVE field is set to zero (0) for the '_D', '_W', '_M' tables. These tables are not being populated with data.

Steps to Reproduce:

1. Login to Clarity as an administrator user
   
   
2. Admin Tool > Studio: Objects > Select any object
   Any object can be used, Project Object used for testing
   
   
3. Attributes > click 'New' button
   Attribute Name : myTSV100
   Attribute ID : myTSV100
   Data Type : Time-varying
   Time-varying Data Units : Number
   Time-varying unit conversion : Hours
   Click 'Submit' button
   
   
4. Views > Object Properties [Layout:Edit]
   Add 'myTSV100' to a subpage and save configuration
   Views > Object List [Fields] > click 'New' button
   Display Type : Time Scaled Value
   Click 'Submit' button
   Select the 'myTSV100' attribute and configure for
   Monthly periods and be sure to set 'Allow Grid Editing'
   Save and Publish the configuration changes for this object
   
   
5. Main Application > Projects List View
   The new TSV is shown.
   [--Actions--] Edit Mode
   Enter in some values and save
   
   
6. Ensure that the 'Time Slicing' job has been executed successfully
   
   
7. In a query tool, execute the following query:

   SELECT REQUEST_NAME, FROM_DATE, NUM_PERIODS, EXPIRATION_DATE, IS_SYSTEM, IS_SYNCHRONOUS, TABLE_NAME, IS_ACTIVE FROM PRJ_BLB_SLICEREQUESTSWHERE UPPER(REQUEST_NAME) LIKE '%MYTSV100%' REQUEST_NAME               FROM_DATE  NUM_PERIODS  EXPIRATION_DATE  IS_SYSTEM  IS_SYNCHRONOUS  TABLE_NAME        IS_ACTIVE project::mytsv100::default (null)      (null)         (null)           1            0          ODF_SL_5016051       1 project::mytsv100::day     (null)      (null)         (null)           1            1          ODF_SL_5016051_D     0 project::mytsv100::week    (null)      (null)         (null)           1            1          ODF_SL_5016051_W     0 project::mytsv100::month   (null)      (null)         (null)           1            1          ODF_SL_5016051_M     0 
   SELECT COUNT(*) FROM ODF_SL_5016051 COUNT(*)     -----------  0            SELECT COUNT(*) FROM ODF_SL_5016051_D COUNT(*)     -----------  0            SELECT COUNT(*) FROM ODF_SL_5016051_W COUNT(*)     -----------  0            SELECT COUNT(*) FROM ODF_SL_5016051_M COUNT(*)     -----------  0    

Expected Result: PRJ_BLB_SLICEREQUESTS.IS_ACTIVE = 1 for the ODF_SL_5016051_D, ODF_SL_5016051_W, ODF_SL_5016051_M slice request definitions
Actual Result: PRJ_BLB_SLICEREQUESTS.IS_ACTIVE = 0 for the ODF_SL_5016051_D, ODF_SL_5016051_W, ODF_SL_5016051_M slice request definitions

Solution:

These slice tables are inactive by design. To create slice tables for Daily, Weekly and Monthly intervals, create user-defined Time Slice Definitions through Administration > Time Slices pages.

Keywords: CLARITYKB, CLRT-59101, studio, tsv, attribute, configuration, timeslicing, timeslice, nab.

Environment

Release: ESPCLA99000-12.1-Clarity-Extended Support Plus
Component: