Skip to main content

Follow an updated profile

Overview

When the profile you are referring to is updated to a new version by your organization, you can easily reflect this in your field projects. Even if you have customized the profile to suit your field, you can follow the profile update while maintaining the customization.

The following describes how to follow an updated profile in the following order:

  • Check the change differences due to the update in advance
  • Reflect the change differences due to the update
  • Restrictions

Check the change differences due to the update in advance

When the profile you are referring to is updated, follow the steps below to check the change differences of the profile due to the update.

Check the difference of the updated reference profile

Operation procedure
  1. Click [Profile] > [Tailoring] > [Manage Profile References] from the ribbon to open the [Manage Profile References] dialog.
  2. Select a profile that displays [Update Version] and press the [Update] button at the bottom right.
  3. The [Update Difference] dialog opens and displays a list of the change differences between the versions and the results of the update.
  4. If there are multiple updates from the currently referenced version, you can check the change differences between the selected version by selecting the version to update from [Version after update] at the top left.
  5. If you do not want to reflect the change differences and only check in advance, press the [Cancel] button to close the dialog.
info
  • If you are using a profile included in an installed package by referencing it, you must update the package to the latest version in order to use the latest version of the profile.
tip
  • Click [Export to Excel] from the menu above the list of change differences to record and confirm the same contents as the list display in an Excel file.

Excel export of update change differences

Reflecting change differences due to update

When the referenced profile is updated, follow the steps below to reflect the change differences of the profile due to the update in the project.

Reflecting change differences due to update

Operation procedure
  1. The [Update Differences] dialog box opens, just like in Preview change differences due to update above.
  2. Check the version to be updated in [Version after update] in the upper left, and check the result of the update in the [Update result] column of the list.
  3. Click the [OK] button to reflect the changes to the project. It is not possible to reflect only a portion of the change difference.
caution
  • If a class is deleted from the metamodel by updating, the model corresponding to that class will also be deleted.

  • If a view definition or shape definition of a diagram is deleted by updating, the information such as the position, size, and style of the shape on the diagram will also be deleted.

Restrictions

  • About update operation

    • If the profile has been customized and changed, and a similar change has been made in the update, and there is no difference with the customization result, the record of the change by the customization will disappear and it will no longer be displayed as a change difference.
    • If the update causes a valid column to no longer exist in the grid included in the view definition, the definition of that grid will become invalid and will no longer be displayed on the view.
    • If the profile has been customized to disable the enumeration value of the enumeration type, and the update causes the enumeration type to no longer have a valid enumeration value, the customization that disabled the enumeration value will be canceled and it will be displayed in the selection.
    • If you have customized a profile and changed the order of elements, and a conflict occurs when you update and change the order of elements in the update, the order after the update may differ from both the customization and the update.
    • If the parent of an element has changed before and after an update, it will not be displayed as a change difference, but the parent change will be reflected in the update.
  • About conflicts during updates and how to resolve them

    • If there is a conflict between changes made by customizing a profile and changes made by updating a referenced profile, the conflict will be resolved and the profile will be updated according to the following rules.

      TargetConditionUpdate result
      Profile element attributeThe same attribute has been changed but has a different value
      (e.g. the display name of a field has been changed to a different value)
      Customized value
      Profile element attributeAn element with a changed attribute has been deleted
      (e.g. a field with a changed display name has been deleted)
      Delete
      Profile elementThe parent of the added element has been deleted
      (e.g. the class to which the field was added has been deleted)
      Delete
      Profile elementAn element that references the added element has been deleted
      (e.g. the class specified for the type of the added field has been deleted)
      Delete
      Profile elementAn element with the same name as the added element has been added
      (e.g. a field with the same name has been added)
      The element remains as is, no changes due to customization
    • Depending on how conflicts are resolved, the result after updating may differ from what was displayed in [Update Result] in the [Update Diff] dialog.