Current Period needs to be re-set for ALM models after 8th Aug platform release


When syncing existing ALM models, users will find that the Current Period becomes unset in the Deployed model. This will occur for the first ALM sync after the 8th August Platform Release.


The reason for this is due to the Time Label changes that have been introduced and which are documented here: The changes will appear in the Comparison Report for the first sync, as shown, as they need to be applied to the Deployed model.


comp report changes.PNG


After syncing these changes, please ensure you re-set the Current Period in your Deployed model.


If you need further assistance please contact

Internal Reference: ALM-1463


Best Answer

  • WillE
    Answer ✓

    This issue was resolved following 14th November 2020 release