KB489606: Download and Upload .mstr Files

Historically, .mstr files have been useful for the following:

• Transporting demo dashboards
• Troubleshooting customer issues
• Quickly sharing dashboards across environments

However, .mstr files have known limitations that make them unsuitable for enterprise or production migration, including the following:

• Data size limitations
• No data inclusion for live-connection datasets
• Incomplete behavior when security filters are applied
• Functional gaps compared to Object Package migration workflows

At the same time, Object Package migration in Workstation has matured significantly. Strategy recommends this method for migrating production dashboards.

As a result, .mstr workflows are no longer enabled by default in web clients. They remain available on demand for customers and field teams who explicitly depend on them.

Strategy One (April 2026) Updates

Workstation

• No change：

Downloading and uploading .mstr files in Workstation remains available and unchanged.

Web Clients (Strategy Web / Authoring Web / Strategy Library Web)

• .mstr download and upload entry points are hidden by default.
• These entry points can be re-exposed via a feature flag, if needed.
• These updates applies to the following products:
• Strategy Web (Authoring Web)
• Strategy Library Web

There is no user-facing warning or messaging when the functionality is disabled—entry points are simply hidden.

When Should You Use .mstr Files?

.mstr files are considered legacy, maintenance-only workflows and are not recommended for production migration.

.mstr files may still be appropriate for the following:

• Sales Engineering demos
• Consulting enablement
• Support troubleshooting
• Non-production, short-lived workflows

For production dashboard migration, customers should use Object Package migration workflows in Workstation.

Re-Enabling .mstr Workflows in Web Clients

For Strategy Web (Authoring Web) and Strategy Library Web, .mstr functionality can be re-enabled using either a client-side or server-side feature flag.

If either the client flag or server flag is enabled, .mstr upload and download functionality will be exposed.

Client-Side Feature Flag (Browser-Only)

1. Open Strategy Web or Strategy Library Web in a browser.

2. Open the browser’s Developer Tools.

3. Click the Console tab.

4. Run the following command:

localStorage.setItem('supportMSTRFile', 'true')

5. Refresh the page.

.mstr functionality is enabled for the current browser session.

Server-Side Feature Flag (Persistent)

Strategy Web (Authoring Web)

1. Add the following entry to WEB-INF/xml/sys_defaults.properties:

Note: Create the file if it does not exist.

supportMSTRFile=1

2. Restart the server.

Strategy Library Web

1. Add the following entry to WEB-INF/classes/config/configOverride.properties:

features.supportMSTRFile=true

2. Restart the server.

Important Notes

• Existing .mstr file limitations remain unchanged.

• .mstr workflows are not certified for producton migration.

• The feature flag is supported for users who explicitly require it.
• Usage may be monitored to help inform future product decisions.