File Compatibility

Overview

Next Design files have versions for the data they hold.
The file-level data version held by a file is called the schema version.

Next Design has a supported schema version for each version, and can handle files of the corresponding schema version.
However, because Next Design has file compatibility, it can also handle some files of versions other than the corresponding schema version. The behavior when opening files of unsupported versions is as follows:

Behavior when opening files of unsupported versions

Opening files of older schema versions

Next Design can open files of older schema versions. Therefore, immediately after a Next Design version upgrade, you can open files of older schema versions with a new version of Next Design.

Note

• When saving a file, the file's schema version is updated to the corresponding schema version of Next Design. Please note that after updating a file with a new version of Next Design, it may become impossible to open it with an older version of Next Design.

Opening a file with a new schema version

Next Design can open files with a new schema version only if they are within the same major version. Therefore, even if the Next Design versions used in a large-scale development environment differ slightly, files created by other teams can be accepted.

Opening a file with a new major version
Next Design cannot open files with a new schema version in its major version. A notification dialog like the one below will appear; please update to Next Design that corresponds to the schema version displayed in the dialog.

Opening a file with a new minor version
Next Design can open files with a new schema version in its minor 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 an older version of Next Design

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

Next Design Supported Schema Versions

Next Design	Schema Version
V1.1	9.0
V2.0	11.0
V3.0	11.1
V4.0	13.0
V5.0	13.1

Change History (Schema Version)

Schema Version	Summary of Changes	Attribute Name	Path (JSON format)
9.0	-	-	-
11.0	-	-	-
11.1	[Add] Specify information for the model to be checked (Trace View Settings)	ModelIds	Project/Settings/Trace/TraceTreeSettings/Targets
	[Add] Specify information for the trace line to be checked (Trace View Settings)	RelationshipClassIds	Project/Settings/Trace/TraceTreeSettings/Targets
13	When opening an older version of a project file, the rich text data will be updated as follows: ・Convert rich text saved in XAML format to HTML format. ・Convert non-XAML strings saved in XAML format to HTML format. ・Convert XAML rich text saved in HTML format to HTML format. ・After conversion to HTML format, the XAML data will be deleted. ・Remove unnecessary tags and styles specific to the old format that are included in HTML created in the old format.	-	-
	[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-dependent information)	ProfileReference	ProfilesMetamodels/Packages
	[Add] Tailoring Information (Change Log)	Tailorings	Profiles
	[Add] Migration Information (ID conversion information generated when converting to reference format, etc.)	Migrations	Profiles
	[Add] Setting to output compatibility information (Model file sharing information)	OutputCompatibleFormat	None (Attribute directly under the 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.) (Each view element only has a DefinitionName)
13.1	[Add] Document Output Settings (View Definition Information)	ExportDocument	Profiles