and
linked models.
You should also ensure that data source connections have not changed
and that data sources are online. You can check your connections by
testing a few key query subjects.You can use Framework Manager log files to synchronize your project. You may choose to synchronize your project if you
updated metadata in a third party modeling tool.
made changes to metadata using a multidimensional modeling tool.
When you synchronize your project, you create a new project by replaying from the log files, all the actions you made in the original project.
Special considerations should be taken before synchronizing projects that contain segmented models, linked models, or repository connections.
If your data source is a relational database, you can update only the query subjects and do not need to perform a full project synchronization. You must perform a project synchronization to synchronize changes made in a third party data source.
If you import a subset of a data source, any new objects that were added to the data source are not included when you synchronize. The action log recorded the importing of objects that you originally specified. When you synchronize, only the originally imported objects are re-imported.
You can use project synchronization to run the complete action history of the model and update the model's metadata. You can also save portions of the action log to a separate script file for later use, or you can save the entire action log to a script file if you want to build the same model in batch mode. If you encounter errors when trying to run an action log script, see Fixing Errors Caused by Invalid Objects.
After synchronizing, you can choose to accept the new changes and create a new project, or return to the original project. If you accept the new changes, the original project is replaced.
Because every action that you made in your project is rerun, synchronization may take a long time.
If an object that is referenced by a transaction no longer exists, either because it was renamed or deleted, you will receive errors during the synchronization. For example, if you imported a table named Products and then renamed the table to New Products in your data source, you will receive an error when you synchronize the project. The synchronization cannot detect that the table named New Products was previously imported using a different name. You must manually retarget the object to complete the synchronization. For information about fixing synchronization errors, see Fixing Errors Caused by Invalid Objects.
Note: Action logs from Cognos ReportNet are not supported in this release.
Before synchronizing a project, you should understand how synchronization
impacts segmented and
linked models.
You should also ensure that data source connections have not changed
and that data sources are online. You can check your connections by
testing a few key query subjects.
A segmented model should be synchronized only by synchronizing the main project. The results of synchronizing the entire project are written to the log file of the main project. The ability to synchronize individual segments is lost after the first synchronization of the main project.
If you are working in the main project and change a segment, the main log file is updated. If you are working in the segment and make changes, the segment log file is updated.
Synchronization commands do not necessarily run in the order they appear in the log files. This happens because it is possible to update segments concurrently and the action logs are replayed based on the time of the original action. Commands may appear to jump between log files, making it difficult to use debugging features such as single stepping.
Log files are contained in the project that is open and not in the model that is updated.
If you open a main project and make changes to a linked model, the actions are logged in the log file of the main project. If you then synchronize the linked model, the change is lost because it did not appear in the set of log files that were used in the synchronization.
Synchronization can be run only on the main project or a stand-alone segment. You cannot synchronize linked projects or segments in the main project. If the segments are updated by the linked project, the synchronization can produce unpredictable results in the main project.
We recommended that you do not use model synchronization in combination with linked projects.
We do not recommend synchronizing projects that are connected to repositories. If you do synchronize repository projects, you should consider the following.
All repository information will be removed from the project after the synchronization is complete.
You must manually remove the project from the repository and use Framework Manager add the project back to the repository. All revision history will be lost.
Synchronization will not be successful if the project was not added to the repository in the correct way.
If you plan to synchronize a segment belonging to a repository project, you must first create the segment and use the Add Project to Repository action on the Repository menu. You should not add the project to the repository using the Create Project dialog box.
If you use the View History action to revert to a previous version, the log files for the revisions that were supposed to be reverted are left intact. Without intervention, synchronization will execute these log files and will not correctly produce the intended revision. To successfully complete the synchronization, you will have to manually identify and remove the log files.
From the Project menu, click Synchronize.
We recommend that you create a backup of your Framework Manager project by selecting the Backup project into this directory check box.
If you want to view the details of a transaction, click the transaction.
Set the starting or stop point that you want.
To set the starting point for running the
script, select the script and then click Set the starting
point. You can do this at any time to skip an instruction
or run instructions that have already been executed 
.
To set a stop point for the script, select the script and then
click Set the stop point 
.
You can stop the script to make a manual fix and then start it again.
Tip: To remove the stop
point, click Remove the stop point 
.Using the toolbar buttons, choose the run action that you want.
Button | Description |
| Runs the script After an error is encountered, clicking this button attempts to re-execute the failed instruction. |
| Skips to the next transaction and runs the script to the end |
| Runs the selected transaction only |
| Skips to the next transaction and stops, but does not run any transactions |
The project window is updated as the script is run.
Fix any errors encountered by the script either by retargeting objects or modifying the temporary project as required.
For more information, see Fixing Errors Caused by Invalid Objects.
When the script has completed, click Accept.
The original project is replaced by the contents of the temporary project.
Tip: To return the project to its previous state, click Revert.
