Time Slicing Sync with force option (Best Practices and Use)

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

The job Time Slicing Sync is currently scheduled without the force option. What are the best practices regarding this job with this parameter? 

Environment

Any Supported Clarity Release

Resolution

• Time Slicing Sync job with force flag will reslice all the SQL Curves in the system
• As such, it may take long time on large datasets, and have to recreate the TSV data
• We do not recommend running this job with force as a regularly scheduled job unless you would like to resolve a specific data discrepancy
• Data discrepancies that will be addressed by running this job may include:
  • Wrong or blank Total fields on Per Period metrics in Staffing and other MUX screens
  • Discrepancy in the same data between different screens such as Project metrics vs the same project in Roadmap
  • Missing or incorrect data on some Months / periods only
• If you face a one off discrepancy, we recommend to run the Time Slicing Sync job with force flag and nothing else is required
• If you see an ongoing reoccurring problem, you can run the job more frequently, and try to establish specific steps to follow and engage Support