Partial loading of model files

Restrictions

If you open a project that has model files set to manual load, those model files will be unloaded. The restricted functions and their restrictions in this state are:

Feature	Constraints
Save As	Cannot be executed if there is even one unloaded model file. Please load all model files and then run for the function to work.
Find	Finds loaded model files, but not unloaded model files.
Model error check	If there is even one model file that has not been loaded, the existence of the related destination model will not be checked when executing the error check. Also, unloaded model files are not checked for errors.
Show Diff	Compare only the loaded model files. Also, if the files to be compared have different file configurations, the comparison results may not be as expected.
Export Model File	If there is even one unloaded model file in the export target, it cannot be executed. To run the function, load the model file and then run it.
Integration of model files	If there is even one unloaded model file in the integration target, it cannot be executed. To run the function, load the model file and then run it.
Start of product line	If there is even one unloaded model file, it cannot be executed. Please load all model files and then run for the function to work.
Edit profile	If there is even one unloaded model file, it cannot be executed. Please load all model files and then run for the function to work.

Partial load nodes and caveats

If the parent of a model is contained in an unloaded model file and does not exist in the model navigator, a node labeled [Partial Load] will appear at the bottom of the model navigator, and below that will be the unloaded model and its parent. Subordinate models are displayed. These nodes are called partially loaded nodes.

Limited functionality

Even if you specify the entire project as the scope of the following functions, the model corresponding to the partial load node is excluded from the scope.

• search
• Error checking
• document output

model path

At the top of Next Design's editor is a path bar that displays the path of the model. Note that the path bar normally shows the absolute path from the root of the project, but the model shown under the partial load node will show a different path.

• ":partial" is added to the beginning of the path for models displayed under the partial load node.
• When the load status of the model file changes, the path changes from the partial load node and below.

Memorize user preferences and notes for projects

Partial load settings are remembered in the {project file name}.nuser file in the same folder as the project file.

When using a configuration management system, please note the following about handling .nuser files.

In addition, since it is necessary to understand the above-mentioned restrictions when using partial loading, it is recommended that all team members are aware of this before sharing the .nuser file.

Notes on Subversion

• When registering a project in Next Design, .nuser files are excluded from configuration management.
• If you want to manage the configuration of .nuser files, use a tool other than Next Design to register and commit manually.
• Changes to .nuser files will not show up in Next Design's list of commits.

Notes on Git

• Unless you want to share partial load settings with all team members, register the .nuser file in the .gitignore file to exclude it from configuration management.

Common notes

• Unloaded model files are not subject to error checking. Please load the model file you want to target and then execute.