Find Answers

Filter Search Results
All Operating Systems:
All Products:
All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Edit problem after BACKOUT after installing Package 100
Customer receives messages: CHANGES WILL BE LOST and COMPONENT OUT-OF-SYNC when trying to edit and stage a backed out component. This is when the VALIDATE VERSION DURING STAGING parm is equal to YES.
CMS-XML Message CMN2556A (changes will be lost) not produced for new components
Message CMN2556A ( changes will be lost ) not produced for new components
CMS-XML Invalid message "CHANGES WILL BE LOST" issued when trying to edit/stage new component.
Invalid message " CHANGES WILL BE LOST " issued when trying to edit/stage new component.
CMS-XML ERO: Invalid CMN2556A (changes will be lost) editing comp from prior release
ERO: Invalid CMN2556A ( changes will be lost ) editing comp from prior release
CMS-XML The investment could not be saved because it was edited by another user. the investment will be reloaded and you changes will be lost
The investment could not be saved because it was edited by another user. the investment will be reloaded and you changes will be lost
CMS-XML Allowed to edit component in ZMF4ECL even though ‘CMN2556A’ message in ZMF
In ZMF, if a baseline component has changed since you checked out the component in your package, when you attempt to edit the component get ‘ CHANGES WILL BE LOST ’ and the long message ’CMN2556A - Check out new version from baseline; changes will not be saved.’ In ZMF, when staging (BUILD) the same component you get ‘COMPONENT OUT-OF-SYNC’ and the long message ‘CMN2555I - The baseline version of ABC101.SRC has been modified’.
CMS-XML Inconsistent behaviour of checkout from promotion with CMN2556A
When checking out components from promotion various methods work differently with relation to further edits, 'validate version during staging' processing and the following error: CHANGES WILL BE LOST /CMN2556A - Check out new version from baseline; changes will not be saved. The processing varies between releases, too. Attempts to edit a component after checking it out from promotion in an application with VALIDATE VERSION DURING STAGING ===> YES in ZMF 5.6(.3) result in the following:
CMS-XML Batch checkout with validate version
Validate Version during staging is set to Yes They perform a batch checkout of a component that does not have baseline stats. If they try to edit the component, they receive " Changes will be lost ". “CMN2556A - Check out new version from baseline; changes will not be saved.”
CMS-XML It is possible to edit the text field defaults of a checked in field within composer
It is possible to edit the text field defaults of a checked in field within composer. These changes will be lost on check out of the field in question.
CMS-XML Unexplained SYNCH11! errors in audit
Whilst resolving this issue it became apparent that the underlying cause may also result in missing " CHANGES WILL BE LOST "/"CMN2556A - Check out new version from baseline; changes will not be saved." messages during component staging processing. These messages should be issued when there is a possibility of change regression and the 'Validate version during staging' option is enabled in application admin.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs