Exporting a package to a separate project is the first step of model decomposition. Then you can reuse that project in other projects. You can export a package to a new server project if you need to detach a part of the model from the project. The part can be a library or a fragment of the model simultaneously developed by another team. You can use the part of the model you moved in more than one project.

To export a package to a new 3DEXPERIENCE server project

  1. In the Model Browser, right-click the package to export.
  2. Select Project Usages > Export Packages to New Server Project. The Export Packages to New Project dialog opens. The package is already selected in this dialog.
  3. Click OK.
  4. If there are any cyclic dependencies, they are shown in the Package Dependencies panel:



    You cannot export the package if it has cyclic dependencies. Eliminate the cyclic dependencies before trying to export the package again.
  5. If no cyclic dependencies are detected, you see a dialog with the options to change the package name and/or add a commit comment. Make any necessary changes and click OK.
  6. Wait for package export to finish.
     

If packages being exported from the source project to the target project are dependent on other elements that are NOT exported together, the necessary usages to used projects are created in the project these packages are moved to. This is being done with the intention of keeping all the dependencies valid.


The newly created server project has the structure and the contents of the exported package and is automatically used in the project from which it was detached. The used project appears under the package Project Usages in the Model Browser, and the exported package no longer appears under the root package in the Model Browser.

You can reuse the newly created server project in other projects.