User Help > Managing Source Files as Members > Setting the Default Member Revision
Setting the Default Member Revision
CLI  
si updaterevision
You can update a member revision without checking in a member by using the Update Revision command.
The member revision is the default revision that users work with in all other Sandboxes. For example, if demoapp.c 1.1 is the member revision, setting 1.2 as the member revision makes it the default revision in all Sandboxes.
For example, code freeze has been reached on the stock calculator, and Steve has frozen all of the members in that project. After all the project members are frozen, Quality Assurance tests the code. In this case, they find a bug in the stock calculator. Steve must now incorporate the fix into the project by thawing the member revision, updating it to the head revision, and freezing it again.
You can update the member revision to a pre-selected or pre-defined revision. This is useful when you want the member revisions in a project to reflect revisions based on a symbolic location in the development path (working file, head revision, trunk tip, or member branch tip) or property (state, label, or timestamp).
Interface
Procedure
GUI
Select Member > Update Member Revision.
Web
Select Member > Update Revision.
* 
You cannot update a frozen member revision. You must first thaw the member revision and then update it.
From PTC RV&S 13.5.0.0 onward, the maximum length for a member revision ID has increased from 160 to 250 characters. If you use an older client with a 13.5.0.0 server and try to work with a member whose revision ID is longer than 160 characters, an error appears. This is because the older client cannot handle revision IDs longer than 160 characters. To ensure compatibility and avoid such errors, upgrade the PTC RV&S client to the latest version when working with projects that include member revision IDs greater than 160 characters.
Was this helpful?