Tag Archives: part

Dr. Dobbs Journal: The Corruption of Agile – Part 1 of 3

Readers:

I have been in the Computer Science / Information Technology / Management Information Systems profession a long time. There are times when I need to take a break from all of the noise going on in our profession and revisit words and thoughts from the people I consider my mentors. These are the people who helped me become a better programmer, a better thinker, and learn to question everything.

One of my favorite magazines that I have read since my early days in this profession is Dr. Dobbs Journal. Reading articles in this wonderful magazine from many of the thought leaders (e.g., Scott W. Ambler, Allen Holub, Bruce Eckel, Larry O’Brien, Dave Thomas, Andrew Koenig, etc.), who taught courses early on at various conventions I have attended during my actual computer language programming days (e.g., C, C++, Java), remind me of the principles and personal practices I have let slip or ignore with all of our new drag-n-drop GUI-related tools.

Andrew BinstockI came across this article from Andrew Binstock (photo right), who is the Editor in Chief of Dr. Dobbs Journal. Prior to joining Dr. Dobb’s Journal, Andrew Binstock worked as a technology analyst, as well as a columnist for SD Times, a reviewer for InfoWorld, and the editor of UNIX Review. Earlier, he was a senior manager at Price Waterhouse. He began his career in software development in the early 1980’s.

I have included Mr. Binstock’s recent editorial about his concerns about how we are corrupting Agile in it’s entirety below. In Parts 2 and 3 of this series, I will explore some interesting thoughts about the Agile Manifesto and an interesting technique developed by Dave Thomas to continuously improve our programming skills.

Best Regards,

Michael

The Corruption of Agile

by Andrew Binstock, Editor in Chief, Dr. Dobbs Journal

What was intended as a set of personal practices has become a doctrine. And despite the mainstream adoption of Agile, the loss of its original intent has undermined its effectiveness.

Many people over the years have discussed their distress with the religious tone that cloaks the implementation of Agile practices. Particularly from the testing side of the world, there is a lot of “should,” “should not,” and “can do better next time” dialogue that sounds more like a man trying to fix ethical lapses than a developer writing code. When I speak with adherents of test-driven development (TDD) in particular, there is a seeming non-comprehension that truly excellent, reliable code was ever developed prior to the advent of this one practice. I sense their view that the long history of code that put man on the moon, ran phone switches, airline reservation systems, and electric grids was all the result of luck or unique talents, rather than the a function of careful discipline and development rigor.The disconnect between today’s Agile view and earlier reality is equally evident in the wanton bashing of the waterfall model. To get any programmer today to adopt your recommendation, simply state that not doing so is just a new way of doing waterfall. Watch his toes curl despite never having used waterfall, nor seemingly having any awareness that it served the industry really well for decades. What, was everyone in that bygone era a fool?Alan Kay was entirely right when he said that programming today has become a pop culture: “Pop culture is all about identity and feeling like you’re participating. It has nothing to do with cooperation, the past or the future — it’s living in the present. I think the same is true of most people who write code for money. They have no idea where [their culture came from] — and the Internet was done so well that most people think of it as a natural resource like the Pacific Ocean, rather than something that was man-made. When was the last time a technology with a scale like that was so error-free?”

It will pain some readers to know that the vast, error-free Internet predates Agile and even predates TDD. Crazy, right?

What I’m saying here is certainly not new. The fascination with today’s way of doing things and the view that it is the one true path to good code is a seemingly permanent part of the programming culture. But it has been greatly abetted by the legions of Agile consultants. By stressing the practices, they have corrupted what Agile was about. It’s important to remember that the Agile manifesto stated values, not practices. Immediately, though, values were translated into programming practices by consultants and, quickly, the former was lost. One of the original formulators of the manifesto, Dave Thomas, whom I interviewed this week, states his realization that a month after the manifesto was written it was already being corrupted: “…it got immediately productized in many different ways. The whole point, to my mind, of the Agile Manifesto is that it’s a set of personal practices that may scale to team level. You do not need a consultant to show you how to do that. It may help to have someone facilitate, but you do not need a consultant. And yet immediately what happened was that everyone and their dog hung out an Agile shingle and the whole thing turned into a branding exercise.”

What’s interesting in Thomas’s account is the view that Agile was a personal practice. Implicit is a personal way of orienting oneself towards a development process that accepts, even welcomes, change.

By pure coincidence, Allen Holub has been driving this point home in several blog posts, the most recent of which is a brilliant little piece that reminds us that Agile is a culture, not a set of practices. As he has previously explained, just because an organization is using scrum, doesn’t mean it’s Agile. He could have said the same thing about TDD, continuous integration, pair programming, or the like.

Whether a site is Agile or not depends on its culture. Does the culture support the personal values of the manifesto? If so, it’s Agile, if not, then it’s doing something else. So, indeed you could have a fully Agile site without TDD, continuous integration, or scrum. Likewise, you can have a site that uses all three practices, but cannot adapt to changes and is wholly inflexible in its work — so, not at all Agile. Yeah, I know, crazy, right?

Next: What the Agile Manifesto Really Said

———————————————————————————–

Source: Andrew Binstock, The Corruption of Agile, Dr. Dobbs Journal, March 18, 2014, http://www.drdobbs.com/architecture-and-design/the-corruption-of-agile/240166698.

Andrew Binstock can be reached at alb@drdobbs.com or via Twitter at platypusguy

Commentary: Some Thoughts on my MicroStrategy v9.4.1 Upgrade Installation on my Laptop – PART 3

Readers:

I am back to continue and finish this three-part commentary about installing MicroStrategy v9.4.1 on my laptop.

Just also wanted to let you know that v9.4.1 Hotfix 2 was released on 02/12/2014 and is now available. I recommend you get your v9.4.1 GA version all up and running properly before you consider installing the Hotfix.

Best regards,

Michael

Reviewing Upgrade Prerequisites

Before you begin upgrading your MicroStrategy system, it is always a good practice to review the MicroStrategy Readme document so that you are aware of any changes from previous releases. You should also review the system prerequisites outlined in the Planning Your Installation chapter of the MicroStrategy Installation and Configuration Guide.

If you do not review the MicroStrategy hardware and software requirements before upgrading, you may experience problems with the upgrade.

Database and Driver Requirements

Refer to Certified and Supported Configurations in the MicroStrategy Readme for updated information about specific database and driver combinations certified by MicroStrategy.

System Sizing Guidelines

There are several factors to consider when you initially set up your MicroStrategy system. These factors include the number of users that will access the system, report complexity, and whether or not you should employ caches. You should periodically re-evaluate your system and update it based on actual system performance and use.

In particular, before updating your metadata (see the Update the Metadata section below), MicroStrategy recommends that you have an amount of free disk space equal to at least twice the on-disk size of the metadata database.

A complete discussion of system sizing guidelines is beyond the scope of this blog entry. Refer to the Planning Your Installation chapter of the MicroStrategy Installation and Configuration Guide for the latest details about sizing your system.

Due to performance improvements and enhancements, MicroStrategy version 9 may require more memory than version 8 for comparable functionality. In particular, if your MicroStrategy 8.x system is running on Windows and is approaching the 3 GB Windows memory limit, you may need to upgrade your Intelligence Server machines. For more information on MicroStrategy memory recommendations, see the system requirements in the MicroStrategy Readme and the Tuning chapter in the System Administration Guide.

Privileges and Access

Before upgrading, ensure you have the following:

  • If you are installing on a Windows system, you must have a login account with administrative privileges for the domain or target machine.
  • MicroStrategy Intelligence Server installation files. You can access the installation files from a disk or from a network location.
  • Write permissions in the installation directory; otherwise the installation/upgrade process fails.
  • If you have purchased a CPU-based MicroStrategy license and are installing on UNIX or Linux, you need root access permissions for installation.
  • A license key from MicroStrategy for the version of the MicroStrategy software that you are installing.

Checking for Supported Data Types

MicroStrategy Analytics Enterprise supports a wide variety of data types for each supported warehouse database. However, some pre-Analytics Enterprise projects may contain data types not supported in MicroStrategy Analytics Enterprise. If a project containing columns with unsupported data types is upgraded, the data types for those columns are assigned as “reserved,” and proper data types are not assigned in temporary tables. This affects report execution.

Before proceeding with the upgrade, you must ensure that all data types assigned in the pre-Analytics Enterprise project are supported in MicroStrategy Analytics Enterprise.

See the MicroStrategy Project Design Guide for a listing of the supported data types for each database type and additional information about changing to supported data types.

Backing up the Metadata

Although the MicroStrategy installation process itself does not affect your project’s metadata, MicroStrategy recommends that you back up your metadata before any significant installation or upgrade. In most major MicroStrategy upgrades, a metadata update is required for all the pre-existing projects in your metadata. Once you update your metadata project, you cannot revert that metadata to a previous version. Therefore, MicroStrategy strongly recommends that you perform a full database backup of your original metadata prior to the upgrade.

MicroStrategy strongly recommends that you also tape backup, image, or ghost the production server before upgrading.

If you want to keep an old MicroStrategy Tutorial metadata repository and warehouse from a previous MicroStrategy version, rename the Microsoft Access files or move them to another location; otherwise, they are overwritten during the installation process. The Access files are installed by default in the MicroStrategy\Tutorial Reporting folder.

Updating the Project Metadata

MicroStrategy requires that you use the Configuration Wizard to update a metadata project created in a pre-Analytics Enterprise version of MicroStrategy to the latest version.

Be aware of the following:

  • If you are upgrading a MicroStrategy 8.x metadata that is stored in a DB2 UDB for z/OS database, refer to MicroStrategy Tech Note TN32695.
  • For assistance with updating MicroStrategy metadata projects from versions prior to MicroStrategy version 8.1.0, contact MicroStrategy Technical Support.

MicroStrategy requires that you update projects through an Intelligence Server connection (3-tier). Upgrading your project using a direct ODBC connection (2-tier) is not supported.

If you do not upgrade the metadata to the latest version, certain features will not work as expected. For example, if MicroStrategy Web Analytics Enterprise connects to a pre-Analytics Enterprise metadata through an Analytics Enterprise server, Change Journaling, Distribution Services, and some Report Services enhancements may not be available.

Downgrading Metadata Projects

Downgrading a MicroStrategy metadata or project to any previous product version is not supported. Once you update the project metadata to the latest version, you cannot downgrade to earlier product versions. Therefore, backing up the metadata is an essential step in the upgrade process as it allows you to revert to a backup version of the metadata, if necessary, to obtain pre-update versions of the projects it contains.

Configuring an Upgrade Test Environment

Your MicroStrategy environment includes multiple variables, such as security requirements, performance requirements, and VLDB settings, that are unique. MicroStrategy cannot anticipate all the ways these variables may interact with the upgrade process. Thus, MicroStrategy recommends you create a test environment and upgrade that environment first, then thoroughly test the upgraded installation. Once the tests are complete, then upgrade your production environment. This ensures that the upgrade of your production environment proceeds smoothly and any unexpected difficulties do not require additional downtime.

I will post a blog in the near future about testing your upgraded environment.

If you do not want to create a test environment, MicroStrategy recommends that you create and save an Integrity Manager integrity test baseline of your reports and documents. You can then execute an integrity test against this baseline when the upgrade is complete, to ensure that the upgrade has not altered any of your report results. For detailed information about using Integrity Manager to execute integrity tests, see the Integrity Manager chapter of the MicroStrategy System Administration Guide.

Best Practices for Configuring an Upgrade Test Environment

MicroStrategy recommends that you follow these best practices for configuring your upgrade test environment:

  • Do not modify any existing configuration objects. If you need additional configuration objects for testing, you can either create additional objects, or duplicate an existing object and modify it. This applies to database instances, connections and logins, security filters, users and user groups, and security roles.
  • If your production environment is clustered, then your test environment should also be clustered.
  • If your test and production data warehouses have different database table prefixes, make sure you are using the correct prefixes in the test environment’s Warehouse Catalog.
  • Create an integrity test comparing reports from the upgraded test environment with the same reports in the production environment, so that you can easily see where any differences are.
  • If possible, plan to execute data integrity and performance load tests against the production warehouse. This ensures that the test scenarios are as representative of the production environment as possible.
  • If you are creating reports and documents specifically for an upgrade integrity test, create those reports and documents before you duplicate the production metadata.
  • If you are using connection mapping for users to access the data warehouse, check to be sure that all users can log in to the test data warehouse, since user passwords may differ between the test warehouse and the production warehouse.

One way to manage this is to create a new generic database login, and then use the following sample Command Manager script to change users’ connection mappings to use this new login:

ALTER CONNECTION MAP FOR USER “

username” DBINSTANCE “production_warehouse_instance” DBLOGIN “test_login” ON PROJECT “project“;

For steps to use Command Manager, see the Command Manager Help, or the Command Manager chapter of the MicroStrategy System Administration Guide.

  • If you are using Narrowcast Server, make sure that the database copy of the Narrowcast repositories is not used when setting up the Narrowcast Server test environment. Instead, make a copy of the repositories with the Copy Repository utility included with Narrowcast Administrator and use this copy. This ensures that the test environment does not accidentally refer to a production server. For detailed instructions on creating a copy of the Narrowcast repositories, see the Narrowcast Server Upgrade Guide.

High-level Steps to Configure an Upgrade Test Environment

To ensure that your tests accurately reflect the upgrade experience, the upgrade test environment should reflect the production environment as closely as possible.

To Configure a Test Environment

  1. Set up the hardware for the environment. MicroStrategy recommends that this hardware duplicate the configuration of the production environment as closely as possible.
  2. Install your current version of MicroStrategy in the test environment.
  3. Using the Project Duplication Wizard, duplicate the production metadata into the test environment. For instructions on using the Project Duplication Wizard, see the Managing Your Projects chapter of the MicroStrategy System Administration Guide, or see the Project Duplication Wizard Help.
  4. Make sure that your test environment Intelligence Server is connected to your test environment metadata, and not your production metadata.
  5. If you do not intend to execute your tests against a production warehouse, duplicate the production warehouse, and ensure that the test environment points to the duplicate warehouse and not the production warehouse.
  6. Upgrade the test environment.
  7. Test the upgrade. Again, a future blog topic.

Upgrade Deployment Tests

Deploying the upgrade involves installing, activating, configuring, and running the upgrade processes for Intelligence Server, MicroStrategy Web Server, and MicroStrategy Mobile Server, as well as for the metadata, Narrowcast Server, and Enterprise Manager data repositories. These changes, as well as any other procedures that alter the production environment, should be tested when setting up the test environment.

Deployment tests should be performed by MicroStrategy administrators who normally have the responsibility of tuning and monitoring the MicroStrategy installation.

 

Reference Materials

Some detailed information about installing and configuring MicroStrategy products is beyond the scope of this blog entry and can be found in the MicroStrategy Installation and Configuration Guide. The MicroStrategy Installation and Configuration Guide provides detailed procedures on installing and configuring your MicroStrategy system. It also includes important information about installing, deploying, and configuring MicroStrategy Universal products.

In addition, the MicroStrategy Readme contains information about the new products, new features, and bug fixes available in MicroStrategy Analytics Enterprise.

For detailed instructions for upgrading Narrowcast Server, refer to the Narrowcast Server Upgrade Guide.

Commentary: Some Thoughts on my MicroStrategy v9.4.1 Upgrade Installation on my Laptop – PART 2

MicroStrategy Platform v9.4.1

Upgrade best practices

Review the following recommendations to help ensure the success and stability of your MicroStrategy system and projects when upgrading to the latest version of MicroStrategy.

  1. Follow the upgrade order and recommendations outlined in this section, in particular the upgrade checklist found at The Upgrade Process Checklist in the section below. In particular, always upgrade Intelligence Server prior to upgrading client applications such as MicroStrategy Web or Developer.
  2. Create an upgrade test environment by duplicating your production environment and production metadata. Upgrade this test environment and test it before upgrading your production environment.
  3. Do not downgrade MicroStrategy products or components on a machine to previous versions if you have already installed the most recent version of another MicroStrategy product on that machine.
  4. All MicroStrategy products on a machine must use the same version of MicroStrategy. Do not install or upgrade only some MicroStrategy 9.3.1 products on a machine containing older versions of other MicroStrategy products.
  5. Avoid installing MicroStrategy products using services such as Windows Terminal Services, which create a virtual session on the host machine. Always install MicroStrategy directly on the server machine’s physical interface, or by using a remote connection tool (such as Microsoft Netmeeting or Virtual Private Network) that takes full control of the server machine’s interface.
  6. If you are using clustered Intelligence Servers, then to retain stability in your Intelligence Server cluster while upgrading, shut down Intelligence Server on all nodes in the cluster before proceeding with the upgrade. For more information about clustering Intelligence Servers, see the Clustering chapter in the System Administration Guide.
  7. Every node in the MicroStrategy cluster must run the same version of MicroStrategy for the cluster to work properly.

The Upgrade Process Checklist

The upgrade process described in this section involves the following high-level steps. To help ensure a successful upgrade, follow these steps in the order they are presented in this section.

1. Prepare the MicroStrategy system and projects for upgrade

Preparing a MicroStrategy system for an upgrade involves reviewing information specific to your version upgrade, pre-upgrade information and prerequisites, checking for supported warehouse data types, and backing up the production metadata. It may also involve creating an upgrade test environment that duplicates your production environment.

2. Install and configure Intelligence Server Analytics Enterprise and Developer Analytics Enterprise on a test server

In this step, you install and configure MicroStrategy Intelligence Server Analytics Enterprise and MicroStrategy Developer Analytics Enterprise on a test server and then establish a connection to your production metadata.

3. Update the production metadata

In this step, you update the metadata version of your production projects using the test server environment.

4. Perform basic stability testing

In this step, you perform basic testing to ensure the stability and efficiency of Intelligence Server and your updated projects.

5. Install and configure Intelligence Server in the production environment

Once you are satisfied with the status of the latest version of Intelligence Server, and have updated the projects in your test environment, you install Intelligence Server in the production environment.

6. Install remaining MicroStrategy products in the production environment

With the latest version of Intelligence Server installed in your production environment, you now install and configure the remaining MicroStrategy products in your production environment.

7. Test the upgrade, and perform other post-upgrade tasks

After upgrading to the latest version of MicroStrategy, you perform several post-upgrade tasks such as testing the system, activating your installation, checking system licensing and functionality, managing user privileges, and optimizing your MicroStrategy system.

Next: Reviewing upgrade prerequisites

Commentary: Some Thoughts on my MicroStrategy v9.4.1 Upgrade Installation on my Laptop – PART 1

v9.4.1

Readers:

Last night, I installed MicroStrategy v9.4.1 on my laptop. I already have MicroStrategy v9.3.1 Hotfix 3 on it, but want to start experimenting with some of the new features.

I have a 10 seat license that any legitimate business can download and use for free. The link to apply and download the 10 seat version is here.

Before I talk about some of the interesting components of this install, I want to say that this was the easiest and smoothest install (actually, an upgrade) of any MicroStrategy product I have had. I installed the whole enchilada; Intelligence Server, Web Server, Mobile Server, etc.

I hope you find these notes helpful.

MichaelI have some other really interesting commentaries I am working on and hope to be able to share with you soon.

Best Regards,

Michael

Impact of the Upgrade

My scenario involved the following configuration:

MicroStrategy Software:

  • I already had MicroStrategy v9.3.1 Hotfix 3 installed on my laptop.

Laptop Configuration:

  • Windows 7 Professional with Service Pack 1
  • Intel Core i7 CPU @ 2.20 GHz
  • 64-Bit Operating System
  • 6.0 GB RAM
  • 600 GB Hard Disk

Here are a few name/product changes MicroStrategy Made:

  • MicroStrategy v9.4.1 is referred to now as MicroStrategy Analytics Enterprise.
  • MicroStrategy Desktop is renamed to MicroStrategy Developer.
  • MicroStrategy Distribution Services replaces Narrowcast in v9.x.

Upgrading to MicroStrategy Analytics Enterprise can have a significant impact on your system. The sections below cover some of the specific effects of upgrading.

Client/Server Interoperability

MicroStrategy Analytics Enterprise clients and servers are interoperable with MicroStrategy clients and servers from version 9.0.2 and later. However, full feature support may not be available when the MicroStrategy client and server are on different versions. To ensure full feature support, upgrade all clients and servers to MicroStrategy Analytics Enterprise.

MicroStrategy Analytics Enterprise is not interoperable with pre-9.0.2 releases. That is, clients (such as MicroStrategy Web or Developer) from MicroStrategy Analytics Enterprise cannot communicate with servers (such as Intelligence Server or MicroStrategy Web Server) from pre-9.0.2 releases, and clients from pre-9.0.2 releases cannot communicate with servers from MicroStrategy Analytics Enterprise.

If your system is using a version of MicroStrategy prior to 9.0.2, all clients and servers must be upgraded to MicroStrategy Analytics Enterprise at the same time.

All MicroStrategy products on an individual machine must use the same version of MicroStrategy. In my case, since my laptop is my only environment, I will be upgrading all components to v9.4.1. Do not install or upgrade only some MicroStrategy Analytics Enterprise products on a machine containing older versions of other MicroStrategy products. For example, if you upgrade your Intelligence Server to MicroStrategy Analytics Enterprise, and the Intelligence Server machine contains a copy of Developer, make sure you upgrade Developer on that machine to MicroStrategy Analytics Enterprise as well.

In addition, if a MicroStrategy Web client from a version of MicroStrategy prior to 9.3.1 connects to an Intelligence Server from version 9.3.1 or later, a previous version of the MicroStrategy Web search page is shown. To correct this, either upgrade the MicroStrategy Web client to the latest version, or, in the MicroStrategy Web user preferences, change the default start page to any different page, save the user preferences, change it back to its previous value, and save the user preferences again.

MicroStrategy Mobile Client/Server Interoperability

MicroStrategy Mobile clients from MicroStrategy Analytics Enterprise can communicate with Intelligence Server or MicroStrategy Mobile Server from pre-9.2.0 releases. However, full feature support may not be available when the MicroStrategy Mobile client and server are on different versions. To ensure full feature support, upgrade all clients and servers to MicroStrategy Analytics Enterprise.

MicroStrategy Mobile Server Analytics Enterprise and later is not interoperable with pre-9.2.0 client releases. That is, MicroStrategy Mobile clients and apps from before version 9.2.0 cannot communicate with Intelligence Server Analytics Enterprise or MicroStrategy Mobile Server Analytics Enterprise.

New Features and Workflow Changes

This section describes some of the changes in MicroStrategy Analytics Enterprise and earlier that may affect your users’ workflows.

For a complete list of new products, new features, and updates in MicroStrategy Analytics Enterprise, see the MicroStrategy Tech Note “New Features in MicroStrategy Analytics Enterprise.”

The default options for VLDB settings may change between releases. You can determine what VLDB default settings have changed by creating a VLDB settings report for your database type before the upgrade, and comparing it to a VLDB settings report created after the upgrade. For instructions on how to create a default VLDB settings report, see the section on Default VLDB settings for specific data sources in the Supplemental Reference for System Administration.

New features and workflow changes in MicroStrategy Analytics Enterprise

Some of the new features of MicroStrategy Analytics Enterprise that may affect your users’ workflows include:

  • The name of MicroStrategy Desktop has been changed to MicroStrategy Developer.
  • The following predefined security roles have been renamed:
    • The Desktop Analyst security role has been changed to Analyst.
    • The Desktop Designer security role has been changed to Developer.
  • The following privilege groups have been renamed:
    • The Desktop Analyst privilege group has been changed to Analyst.
    • The Desktop Designer privilege group has been changed to Developer.

New features and workflow changes in MicroStrategy 9.4

Some of the new features of MicroStrategy 9.4 that may affect your users’ workflows include:

  • In a document, if you no longer display an attribute that is used to sort data, the data is no longer sorted by that attribute. You can still select that attribute to sort data.
  • When importing data from a file, the Select Linking Object panel is now the Select Attribute Form dialog box.
  • When creating a new Visual Insight dashboard, the Dataset Objects panel is now opened by default.
  • When creating a new Visual Insight dashboard, you are no longer immediately prompted to select a visualization type to add to the dashboard. Instead, a blank visualization is added to the dashboard and displayed.
  • The menu options for adding a new metric to a Visual Insight dashboard have been reorganized. For detailed steps to add new metrics to a Visual Insight dashboard, see the MicroStrategy Web Help.
  • When defining a threshold condition to display data in a visualization, to create a new metric value band, click the horizontal slider bar in the Thresholds Editor.
  • When enabling a visualization to update the data displayed in another visualization, the Enable Filtering on Selection option is selected by default.
  • The options to export a Visual Insight dashboard are now available in the Tools menu, under Export.
  • The Graph Matrix visualization has been combined with the Graph visualization.
    • The graph styles previously available for the Graph Matrix visualization (Bar, Area, Line, Scatter, Bubble, and Grid) are now available as styles for the Graph visualization.
    • In the Graph panel, the Rows and Y-axis areas have been combined into the Vertical Axis area.
    • In the Graph panel, the Columns and X-axis areas have been combined into the Horizontal Axis area.
  • In a Grid visualization, in the Properties panel, the Fit To option is now the Width option.
  • Integrity Manager now retrieves all rows of a report or document at once.
  • In MicroStrategy Office, many locales no longer require the Microsoft Office Multi-Lingual User Interface (MUI) to correctly display prompt values during internationalization.
  • In MicroStrategy Office, if you add multiple outline reports with dynamic grouping to a single Excel worksheet, all those outline reports retain their dynamic grouping. Previously, only the first outline report retained its dynamic grouping.

New features and workflow changes in MicroStrategy 9.3.1

Some of the new features of MicroStrategy 9.3.1 that may affect your users’ workflows include:

  • In Windows, the MicroStrategy folder in the Start menu has been replaced by two other folders. The MicroStrategy Products folder contains the following items:All other MicroStrategy applications can be found in the MicroStrategy Tools folder in the Start menu.
    • Command Manager
    • Developer
    • Integrity Manager
    • Object Manager
    • System Manager
    • MicroStrategy Web
  • In MicroStrategy Web, the look and feel of the interface has been updated. A new navigational icon bar has been added to the Web interface, with options to create quick dashboards, reports, documents, and more. For detailed instructions on using this new interface, see the MicroStrategy Web Help.
  • In MicroStrategy Web, on the toolbar, the floppy disk is now Save for reports and documents. Previously the floppy disk was Save As.
  • In MicroStrategy Web, to share a link to an object, in your personal folder, right-click the object and select Share, then click Email Link.
  • Visual Insight analyses are now referred to as quick dashboards.
  • In Distribution Services, the Use Send Now privilege is no longer required to send a preview of a subscription. The new privilege Use Send A Preview Now is now required to send a preview of a subscription.
  • The MicroStrategy SDK is no longer available to be installed with the MicroStrategy release. The most recent version of the MicroStrategy SDK is available as a free download from the MicroStrategy support site https://resource.microstrategy.com/msdz/default.asp.
  • Update packages can now be hosted on remote servers. Prior to MicroStrategy 9.3.1, update packages were required to be hosted on the Intelligence Server machine. For information about importing update packages, see the Managing Your Projects chapter of the MicroStrategy System Administration Guide.
  • If you are upgrading from MicroStrategy 9.2.1m or earlier, some widgets that were previously created to display on Android tablets may display as grids or graphs on the mobile device. To display these widgets correctly on Android tablets, see Updating Android widgets from MicroStrategy 9.2.1m.

Next: Upgrade Best Practices