Dear All
We had a closer look at Esri Maps for MicroStrategy v2.0 these days.
The new Location Architect feature is usefule but obviously it only works for standalone report grids in MicroStrategy Web. The same grids used in Report Services Documents cannot make use of the Location Architect model. This is a huge drawback as such documents are a widely used method to create interactive dashboards. This means that if we want to use Esri Maps for MicroStrategy v2.0 in MicroStrategy documents each user has to go through the same cumbersome and anoying process of adding and configuring location types and metric styles as in version 1.0 of the plug-in.
Second, as mentioned in this post Location Architect in EM4MSTR v2.0.1 the only way to transport a Location Architect model between projects currently is to copy-paste a piece of JSON code (which first has to be made visible). My MicroStrategy Service Owners laught at me when I showed them this solution. MicroStrategy has the idea of transport packages, created and used by Object Manager, to bring objects from one environment/project to another project. This is the standard, managed way of releasing objects between projects. It can be done without much explanation and can be automated / tracked / governed.
My last point is regarding the new version 10 of MicroStrategy. As this will be the future reporting platform, I am wondering if there are any release plans for EM4MSTR to support MSTR 10?
Best regards
Christoph