File compatibility

Overview

Next Design files have a version for the data they hold.
The version of the file-level data that a file has is called the schema version here.

Each version of Next Design has a supported schema version, and can handle files of the corresponding schema version.
However, since Next Design has file compatibility, it can handle some files of versions other than the supported schema version. The operating specifications when opening files of unsupported versions are as follows.

info

• There is no difference in the schema version depending on the file save format (.iproj/.imdl/.iprof/.iprot/.nproj/.nmdl/.nprof/.nprot).

Operational specifications when opening files of unsupported versions

When opening a file with an old schema version

Next Design can open files with old schema versions. Therefore, you can open files with old schema versions in a new version of Next Design, such as immediately after upgrading Next Design.

Caution

• When saving a file, the file's schema version is updated with the corresponding schema version of Next Design. Please note that after updating a file in a new version of Next Design, it may not be possible to open it in an old version of Next Design.
  

When opening a file with a new schema version

Next Design can open files with new schema versions only if they are within the same major version. Therefore, even if the versions of Next Design used are slightly different in large-scale development sites, it is possible to accept files created by different teams.

When a major version opens a new file
Next Design cannot open files with a new schema version in a major version.
The following notification dialog will be displayed, so please update to Next Design that corresponds to the schema version displayed in the dialog.

When a minor version opens a new file
In Next Design, a minor version can open a file with a new schema version.
However, please note that attribute name data added with the version upgrade will be lost.

Example of opening a file with a newer schema version in a minor version with an older version of Next Design

When opening a file with schema version 11.1 with Next Design V2.0, the attributes ModelIds and RelationshipClassIds added in schema version 11.1 will be lost from the file, as described in this table. As a result, the "specified information of the model to be checked" and the "specified information of the trace line to be checked" will be permanently lost.

Supported schema versions for Next Design

Next Design	schema version
V1.1	9.0
V2.0	11.0
V3.0	11.1
V4.0	13.0

Change history (schema version)

Schema version	Change summary	Attribute name	Path (JSON format)
9.0	-	-	-
11.0	-	-	-
11.1	[Add] Specify the model to be checked (Trace setting information)	ModelIds	Project/Settings/Trace/TraceTreeSettings/Targets
	[Add] Specifying information for trace lines to be checked (Trace setting information)	RelationshipClassIds	Project/Settings/Trace/TraceTreeSettings/Targets
13	When opening a project file from an older version, rich text data is updated as follows. - Rich text saved in XAML format is converted to HTML format. - Non-XAML strings saved in XAML format are converted to HTML format. - Rich text in XAML format saved in HTML format is converted to HTML format. - After conversion to HTML format, XAML format data is deleted. - Unnecessary tags and styles specific to the old format that are included in HTML created in the old format are deleted.	-	-
	[Add] Display Name (Profile Information)	DisplayName	Profiles
	[Add] Description (Profile Information)	Description	Profiles
	[Add] Version (Profile Information)	Versio	Profiles
	[Add] Category (Profile Information)	Category	Profiles
	[Add] Profile Reference (Profile Dependency Information)	ProfileReference	ProfilesMetamodels/Packages
	[Add] Tailoring Information (Change Record)	Tailorings	Profiles
	[Add] Migration information (ID conversion information generated when converting to reference format, etc.)	Migrations	Profiles
	[Add] Settings for outputting information for compatibility (Model file sharing information)	OutputCompatibleFormat	None (attributes directly under unit file)
	[Add] Compatibility information (Model file sharing information: Model)	MetamodelName, ProfileRoute	Entities (for entities), Relations (for relationships)
	[Add] Compatibility information (Model file sharing information: View)	DefinitionName, ProfileRoute	Editors/each view element (Editors/Nodes, Editors/Nodes/Labels, Editors/Ports, Editors/Composites, Editors/Compartments, Editors/Connectors, etc.) (Only DefinitionName for each view element)