Search In: Doc:Documentation: NEXUS Client
Altium DesignerAltium 365Altium MCAD CoDesignerAltium On-Prem Enterprise ServerAltium CircuitMakerAltium CircuitStudioCompany DashboardAltium Infrastructure Server
Ver: Version: 4
43.23.13.0
Close
Suche Search on Documentation
Documentation Altium NEXUS Documentation ... ((Dialog Reference))_AD Dialogs((G to L))_AD

LibraryMigrator_Dlg-SimpleMigrationLibrary Migrator (Simple Migration) _AD

Created: Mai 05, 2022 | Updated: Mai 05, 2022 | Applies to version: 4

Nexus message

This documentation page references Altium NEXUS/NEXUS Client (part of the deployed NEXUS solution), which has been discontinued. All your PCB design, data management and collaboration needs can now be delivered by Altium Designer and a connected Altium 365 Workspace. Check out the FAQs page for more information.

 

The content of this page is applicable only to Altium NEXUS version 4. To select a previous version, use the version selector at the top of the navigation tree at the left.

For information about importing your existing libraries to a Workspace in Altium NEXUS 5 and above, see Importing Existing Libraries to Your Connected Workspace. For information about Simple Mode of the Library Importer, see the Simple Mode section.

The Library Migrator dialog
The Library Migrator dialog

Summary

The Library Migrator (Simple Migration) dialog provides a streamlined process to migrate selected file-based component libraries to your managed content server. File-based component libraries (.SchLib, .PcbLib, .IntLib, .DbLib, .SVNDbLib) can be converted to server-based managed components with the one-click solution that is provided. 

For information regarding the Library Migrator, click here. 

Access

The dialog is accessed when you are signed in to a managed content server in the following ways: 

  • Selecting Tools » Migrate Library in the Schematic Library Editor and PCB Library Editor. 
  • Selecting File » Migrate Library or Tools » Migrate Library in the Database Library Editor.
  • Right-clicking on a library file in the Projects panel and selecting Migrate Library from the context menu. 
  • Selecting a file-based library from the Components panel and choosing the Migrate Library option from the  menu. 
The Library Migrator can be accessed only provided the Library Migrator extension is installed as part of your Altium NEXUS installation. This extension is installed by default when installing the software. In case of inadvertent uninstall, it can be found on the Purchased tab of the Extensions & Updates page (accessed by clicking on the  control at the top-right of the design space then choosing the Extensions and Updates command from the menu).
The file-based libraries that are currently available to the software can be viewed and managed in the Available File-based libraries dialog, which is accessed from the File-based Libraries Preferences option on the   button menu in the Components panel.

Options/Controls

  • Settings -  click to view the default migration settings listed in the Properties panel page. 
  •  - click to customize the migration in the Library Migrator's full GUI mode. By default, all of the parameters from the original source library will be set for migration. The migration configuration for each source library can be adjusted and changed through the Library Migrator's Properties panel.
  •  - click to complete the library migration. 
The results of the library migration, as newly created managed components, can be seen in both the Explorer and Components panels.

Tips

  •  A full and ready-to-use component migration relies on the availability of a Component Template that matches the source component type(s). Suitable templates are available in the server if the Install sample data option was selected during installation.
  •  A source library with an unrecognizable (undetected) component type will be migrated without interpretation, as [library name].Uncategorized component types in a [library name].Uncategorized server folder. Before the migration is run, this can be resolved by applying designator mapping or parameter grouping in the Library Splitting dialog. 
  •  Monolithic libraries are automatically split into sub-groups, where each group represents a type of component in that library. The groups are processed as individual libraries.
  •  Any components that trigger a validation error will be skipped.
  •  Any errors the process has encountered can be viewed in the Migration Report, available from the button when the migration has completed.
If you find an issue, select the text/image and pressCtrl + Enterto send us your feedback.
Content