Applied Parameters: ObjectKind=Project|Action=LibrarySynch
This command is used to update placed instances of components on chosen schematic sheets, with modified information from a source library. This includes Standard Components (those placed from Schematic Component Libraries (*.SchLib), Integrated Libraries (*.IntLib), and server-based components) and Database Components (those placed from Database Libraries (*.DbLib, *.SVNDbLib)). The update feature allows you to pass changes to parameters, as well as model and graphical information.
This command is accessed from the Schematic Editor by choosing the Tools » Update From Libraries command, from the main menus.
First, ensure that one of the source schematic documents for the project whose components you wish to update, is open as the active document in the main design window.
After launching the command, the Update From Library dialog will appear. The dialog provides controls that allow you to fully control not only which components get updated, but also how. You can choose to fully replace the placed instance with that in the library, or just update any of: Graphical attributes, parameters, or models. Full control is available at the parameter-level, to determine which parameters get updated for a component, and how.
The dialog is essentially divided into two pages:
- The first page of the dialog deals with the scope of the update - which source schematic documents are to be included in the update and the specific component types contained thereon. Also on this page, you can define the type of update required. The simplest form of update is to fully replace the components on the schematic sheet(s) with those defined in the source library. Graphical attributes, parameters and model links are all updated directly with the information that exists in the source library (or record and referenced libraries, for database components). Should you wish a little more control over what is updated, you can opt to update only specific attributes (graphical, parameters, models).
For parameter and model update actions, still further control is afforded through the Library Update Settings dialog. Access this dialog by clicking the Advanced button. Not only can you define the default, global update actions for parameters and models using this dialog, but also control which specific parameters and models are included in the update.
After defining the scope of the update as required, and the default actions to be carried out, you could simply click Finish. Should you wish to further refine the update on a per-component basis, prior to generating an ECO, click Next to access the second page of the dialog.
- The second page of the Update From Library dialog presents you with a detailed grid, listing all components instances involved in the intended update process. Whereas the first page of the dialog allows you to specify, at a coarse level, which physical component types get included in the update, this page allows you to fine-tune exactly which component instances of those types get updated. Essentially, the page is divided into three:
- The current instances of components placed on the schematics.
- The source library (or managed content server) that will be used in the update. This is typically the same source library from which the component was originally placed, but you do have the ability to complete change the component for another, in the same, or different library.
- The specific update actions required for each component instance. These will initially be set in accordance with the default action settings defined on the first page of the dialog.
After all update options are configured as required, clicking the Finish button will launch the Engineering Change Order dialog, and a final layer of validation and reporting can be applied. Once the ECO is executed, the changes to the specified component instances are implemented on the affected schematic sheets.
- Although DbLib and SVNDbLib files present as libraries in the Components panel, they are only a source of connection and field mapping - not libraries in the true sense of the word. The update feature passes changes to parameters, symbol and model references in the external database, as well as graphical modifications made in referenced symbol and model libraries.
- Individual parameter-level changes for a component instance will only be shown provided the Full Replace option is disabled and the Parameters option is enabled, in the Actions region of the second page of the Update From Library dialog.
- Definitions on the first page of the Update From Library dialog, and the Library Update Settings dialog are persistent. They are stored in the project file upon saving.
- Definitions on the second page of the Update From Library dialog are not persistent. They will be lost if you go back to the first page, or close the dialog.
- While managed components can be updated (to later revisions), or switched out for different Component Items available in a managed content server, a far more powerful feature to manage these components is the Item Manager.