mstrio-py 11.5.6.101

Python interface for the Strategy One REST API

mstrio: Simple and Secure Access to Strategy One Data

mstrio provides a high-level interface for Python and is designed to give administrators, developers, and data scientists simple and secure access to their Strategy One environment. It wraps Strategy One REST APIs into simple workflows, allowing users to fetch data from cubes and reports, create new datasets, add new data to existing datasets, and manage Users/User Groups, Servers, Projects, and more. Since it enforces Strategy One’s user and object security model, you don’t need to worry about setting up separate security rules.

With mstrio-py for system administration, it’s easy to minimize costs by automating critical, time-consuming administrative tasks, even enabling administrators to leverage the power of Python to address complex administrative workflows for maintaining a Strategy One environment.

With mstrio-py for data science, it’s easy to integrate cross-departmental, trustworthy business data in machine learning workflows and enable decision-makers to take action on predictive insights in Strategy One Reports, Dashboards, HyperIntelligence Cards, and customized, embedded analytical applications.

Table of Contents

• Main Features
• Documentation
• Usage Remarks
• Installation
  • Prerequisites
  • Install mstrio-py Package
    • Issues or Specific Use Cases
• Versioning & Changelog
• Deprecating Features
• More Resources

Main Features

Main features of mstrio-py allows to access Strategy One data:

• Connect to your Strategy One environment using Connection class (see code_snippets)

  Note: to log into Library and use mstrio-py user needs to have UseLibrary privilege.

• Import and filter data from a OlapCube, SuperCube or Report into a Pandas DataFrame (see code_snippets)

• Export data into Strategy One by creating or updating SuperCube (see code_snippets)

Since version 11.3.0.1, mstrio-py includes also administration modules:

• Project management module (see code_snippets) with VLDB settings management (see code_snippets)
• Project languages management module (see code_snippets)
• Server management module (see code_snippets)
• User and User Group management modules (see code_snippets)
• Schedules management module (see code_snippets)
• Subscription management modules including Email Subscription, Cache Update Subscription, File Subscription, FTP Subscription, History List Subscription and Mobile Subscription (see code_snippets)
• User Library module (see code_snippets)
• User Connections management module
• Privilege and Security Role management modules (see code_snippets)
• Cube Cache management module (see code_snippets)
• Report Cache management module (see code_snippets)
• Intelligent Cube management modules (see code_snippets) with VLDB settings management (see code_snippets)
• Security filter module (see code_snippets)
• Datasources and Connection Mapping subpackage for database management (see code_snippets) with VLDB settings management (see code_snippets)
• Job Monitor module for job monitoring (see code_snippets)
• Object management module (see code_snippets)
• Contact module (see code_snippets)
• Contact Group module (see code_snippets)
• Device module (see code_snippets)
• Transmitter module (see code_snippets)
• Event module (see code_snippets)
• Migration module (see code_snippets)
• Schema Management module (see code_snippets)
• User Hierarchy module (see code_snippets)
• Attribute module (see code_snippets)
• Fact module (see code_snippets)
• Table module (see code_snippets)
• Filter module (see code_snippets)
• Transformation module (see code_snippets)
• Metric module (see code_snippets)
• Document module (see code_snippets)
• Dashboard module (see code_snippets)
• Content Cache module (see code_snippets)
• Dynamic Recipient List module (see code_snippets)
• Driver module (see code_snippets)
• Gateway module (see code_snippets)
• Language module (see code_snippets)
• Translation module (see code_snippets)
• Report module (see code_snippets)
• Incremental Refresh Report module (see code_snippets)
• Bots module (see code_snippets)
• Content Group module (see code_snippets)
• Applications module (see code_snippets)
• Fence module (see code_snippets)

Documentation

Detailed information about mstrio-py package can be found in official documentation.

Usage Remarks

• It is recommended NOT to use Anaconda environment. Please see Installation section below for details.
• Currently it is not possible to use mstrio-py package to update cubes created via Web. Unfortunately it is not possible to use any REST API endpoint to check whether cube was created via Web or via REST API to provide some warning. In case of seeing one of the following error messages it is most probable that cube was created via Web and REST API can't handle its update, so if you want to update this particular cube you have to use Web.

When we tried to map the new dataset, we detected that some columns are missing or the data type changed, etc.

We could not obtain the data because the DB connection changed and the table does not exist anymore.

• When trying to download a big IMDB Cube (or a Report based on such Cube) on multi-node environment, sometimes the process may fail. This is due to the characteristic of data retrieval of IMDB Cubes with connection to more than one node on iServer. For now, known workaround is to log out and just simply try again. This type of issue can be identified when seeing any of the following error messages during work with IMDB Cube on multi-node environment:

Cube cannot be found.

(even if previously it was found without issue)

Error getting cube metadata information. I-Server Error ERR001, (ServiceManager: XML syntax error.)

Installation

Prerequisites

• Python 3.10+
• MicroStrategy 2019 Update 4 (11.1.4)+

Install mstrio-py Package

Note: it is NOT recommended to install mstrio-py in an Anaconda environment. For a seamless experience, install and run it in Python's virtual environment instead.

Install latest version of mstrio-py using pip command in Terminal:

pip install mstrio-py

To install a specific, archived version of mstrio, choose the desired version available on PyPI package archive and install with pip, as follows:

pip install mstrio-py==10.11.1

Issues or specific use cases

If there are any issues with the installation process it is possible your setup may differ from usual. In that case, please see below some examples of most common situations and how to resolve them.

In all other cases, please refer to the official Python libraries installation guide.

Offline System or Proxy with Blacklisted PyPI

Note: optimally, you should contact your system administrator and either request access to PyPI or some proxy setup whitelisting all or some of the PyPI libraries.

If your setup does not allow to get packages online directly from Python Packages Index (PyPI) using pip, you can download the package manually and install it locally.

1. download .whl file from here: https://pypi.org/project/mstrio-py/#files
2. in the terminal cd into a folder where you want to install mstrio-py
3. use the command provided below after filling the path
   • py -m tells the terminal to use default install execution of python available locally on the machine
   • --user flag says "install only for my user on this machine"
4. If you have issues with py command, try the same with python instead

cd path/where/mstrio/will/be/installed
py -m pip install --user path/to/downloaded/wheel/file/mstrio-py.whl

No Python or pip Installed on the Machine

You cannot use mstrio-py without Python installed on your machine unless directly via Strategy Workstation.

Versioning & Changelog

Current version: 11.5.6.101 (20 June 2025). Check out Changelog to see what's new.

mstrio-py is constantly developed to support newest Strategy One REST APIs. Functionalities may be added to mstrio on monthly basis. It is recommended to always install the newest version of mstrio-py, as it will be most stable and still maintain backwards compatibility with various Strategy One installations, dating back to 11.1.4.

Features that will be added to the package but require APIs not supported by your environment (I-Server), will raise VersionException.

mstrio-py can be used for both, data-science related activities and for administrative tasks. Former requires at least MicroStrategy 2019 Update 4 (11.1.4), latter works with 11.2.1 and higher.

If you intend to use mstrio with MicroStrategy 2019 Update 3 (11.1.3) or older, refer to the PyPI package archive to download mstrio 10.11.1, which is supported on:

• MicroStrategy 2019 (11.1)
• MicroStrategy 2019 Update 1 (11.1.1)
• MicroStrategy 2019 Update 2 (11.1.2)
• MicroStrategy 2019 Update 3 (11.1.3)

Refer to the PyPI package archive for a list of available versions.

Deprecating Features

When features (modules, parameters, attributes, methods etc.) are marked for deprecation but still accessed, the following DeprecationWarning will be shown (example below). The functionality will continue to work until the version specified in the warning is released.

More Resources

• Tutorials for mstrio
• Learn more about the Strategy One REST API
• Strategy One REST API demo documentation