Changes on TSV fields can be saved on wrong periods when working with different tabs on the same browser causing data corruption

Document ID : KB000124404
Last Modified Date : 24/01/2019
Show Technical Document Details
Issue:
STEPS TO REPRODUCE 

Scenario 1
1.    Create a Project called Proj1
2.    Start and finish as of today 11/01/19
3.    Add a team member and go to the Team > Detail view
    Note the first TSV cell displayed is January 2019
4.    With the Allocation By Period back arrow, move the TSV field one set of periods back
    Note the periods have been shifted
5.    Go to Home > Portfolio Management > projects and  open it on a different tab
6.    Create a project called Proj2 with dates as today
7.    Add a team member and go to the Team > Detail view
    Note the Note the first TSV cell displayed is July 2018 as per the TSV field change in step 4
8.    On Proj2 > Team Detail, shift one more set of periods back
    Note, the first period is now January 18
9.    Enter 40 hours on January 18
10.    Go to the other tab where Proj1 is opened.
11.    Enter 60 hours for the first TSV cell. July 18
12.    Click on Save

Expected results: The 60 hours to be saved in July 2018
Actual hours: The 60 hours get saved in January 2018, the TSV period where we did the changes for Proj1

Scenario 2 
1. Go to Home > Resource Management > Resources 
2. Open any Resource and go to the Allocations tab > Detail 
Note the first period of the Allocation By period TSV (Time Scaled Value) field being Jan 2018 
3. Open the same page for a different resource on a different tab 
Note the first period of the Allocation By period TSV (Time Scaled Value) field being Jan 2018 
4. On the first resource move the TSV field one set of periods to the future 
5. Save the changes and those ate OK 
6. Go to the other resource allocations and enter some figures in January 18 
7. Save the changes 

Expected results: The allocation data to be saved on the correct TSV period cell 
Actual results: data is saved on the period cell where other changes were done. This causes data corruption 
 
Environment:
Any CA PPM release
Cause:
This is caused by DE46446
Resolution:
This is being analyzed by Engineering

Workarounds:
1. Do not open multiple tabs to perform the edits., 
Always use a single tab.
2. If multiple tabs are being used, ensure that before data is entered, you do some navigation through the TSV field
The browser seems to remember what was the last TSV period distribution and where changes were made, so on the second tab, changes will be saved as per previous distribution.
On the second tab, if you navigate with the TSV arrows to future or past periods, once you do navigate, values will be saved on the correct cell.
Additional Information:
Please check the attached DE46446.docx file for complete description and screenshots
File Attachments:
DE46446.docx