Breaking changes

The following changes should be considered before upgrading to this release from an earlier version.

Breaking changes introduced in version 2026 R1

  • New certificate requirements for SQL Server are introduced:
    • Your SQL Server must be configured with a TLS certificate signed by a trusted root certificate authority, and the SQL Server service account must have the necessary permission to access this certificate. Refer to the Microsoft guidance on certificate requirements for SQL Server for further information.
    • Granta MI services are configured to use encryption for SQL Server connections by default. If you previously enabled encrypted connections by specifying Encrypt=True as an additional connection parameter for MI Server Connection, MI Settings Service, MI Selection Service or MI Data Flow Configuration (as recommended in the Granta MI security hardening guidelines), this is no longer necessary.
    • Database connection settings for Granta MI components must include the fully-qualified name of your SQL Server. Use of (local) for the SQL Server name where you have a local SQL Server instance, for example in a test environment, is no longer supported. If you experience database connection issues after upgrading a Granta MI installation that includes a local SQL Server instance, check the database connection settings in the configuration tools for MI Server, MI Settings Service, MI Data Flow, and MI Selection Service, and ensure the fully-qualified SQL Server name is used.
  • MI Admin now communicates with the MI Settings Service directly, instead of going via the Service Layer proxy. In clustered environments, to ensure that requests can be processed correctly, Kerberos authentication must be used.

Breaking changes introduced in version 2025 R2

  • Support for custom authentication methods has been removed.
  • A database schema change at this release means that MI Machine Learning models created in earlier versions can no longer be used. This applies to both trained and untrained models. You will need to create and train new models after upgrading.
  • Default exporters for MI Materials Gateway must now be specified in MI Settings. The settings DefaultExporterGUID and DefaultSimulationExporterGUID in the MI Materials Gateway configuration gateway.config are no longer supported.
  • For hub-and-spoke data configurations (where CAD Materials and Simulation Records are stored in separate tables):
    • Simulation Record tables now have the table type 'Material'.
    • MI Materials Gateway customization settings that apply to 'Simulation Records' are no longer supported. The settings for 'Materials' can be used instead.
    If you have an existing hub-and-spoke data configuration, you will need to make changes to your database schema and MI Materials Gateway configuration. See Granta MI Materials Gateway Installation and Configuration .

Breaking changes introduced in version 2025 R1

  • As a result of updates to the MI Materials Gateway search user interface:
    • Material attributes cannot be configured to appear as default search filters.
    • Searches cannot be saved in MI Materials Gateway, and any previously saved searches cannot be loaded.
  • Reports and dashboards in MI Materials Gateway that provide weight roll-ups and analysis of material assignments (Bill of Materials, Preferred Materials) are no longer supported. Instead, you can use the weight roll-up features of your host CAD or PLM application.
    Note: A BoM with its assignments can still be exported as a file, or viewed in BoM Analyzer (if Restricted Substances or Sustainability is enabled).
  • The BoM Schema version 15/02 (last supported in Granta MI 2023 R2) is now deprecated and cannot be used as an export format in MI Materials Gateway.
  • The Machine Learning API is no longer installed on the MI application server. It is now installed on the MI Machine Learning compute server.

Breaking changes introduced in version 2024 R2

  • Custom curve fitting for exporting from MI Mat Analyzer to Granta MI is no longer supported. Instead, a selection of curve fitting specifications is provided.

Breaking changes introduced in version 2024 R1

  • When exporting a Bill of Materials as a file from MI Materials Gateway, Granta XML BoM Schema versions 10/06 and 14/04 are deprecated, and can no longer be exported.
  • In the Restricted Substances and Sustainability Specification Maintenance configuration (config.json), databases are now identified by database_key rather than database_name. The default is currently MI_Restricted_Substances, and must be changed if your database key is different.

Breaking changes introduced in version 2023 R2

  • Changes to the Async job format in this release mean that any existing completed or queued jobs in the Job Queue cannot be accessed after upgrading. Users should download the results of their completed jobs (reports, exports) before Granta MI is upgraded. Any jobs that were pending must be re-created and re-submitted after the upgrade. The output files for completed jobs are still left on disk on the Granta MI application server in %ProgramData%\Granta\Granta MI\JobQueueRoot\output, and may be retrieved from there after upgrade, if necessary.