Beste allen<\/P>
<\/P>
We hebben de afgelopen dagen Esri Maps for MicroStrategy v2.0 nader bekeken.<\/P>
De nieuwe Location Architect-functie is nuttig, maar werkt duidelijk alleen voor standalone rapportroosters in MicroStrategy Web. Dezelfde roosters die in Report Services Documents worden gebruikt, kunnen geen gebruik maken van het Location Architect-model. Dit is een groot nadeel aangezien dergelijke documenten een veelgebruikte methode zijn om interactieve dashboards te maken. Dit betekent dat als we Esri Maps for MicroStrategy v2.0 in MicroStrategy-documenten willen gebruiken, elke gebruiker door hetzelfde omslachtige en vervelende proces moet gaan van het toevoegen en configureren van locatie-types en metriekstijlen zoals in versie 1.0 van de plug-in.<\/P>
Ten tweede, zoals vermeld in deze post Location Architect in EM4MSTR v2.0.1<\/A>, is de enige manier om een Location Architect-model tussen projecten te transporteren momenteel door een stuk JSON-code te kopiëren en plakken (dat eerst zichtbaar gemaakt moet worden). Mijn MicroStrategy Service Owners lachten me uit toen ik hen deze oplossing liet zien. MicroStrategy heeft het concept van transportpakketten, gemaakt en gebruikt door Object Manager, om objecten van de ene omgeving\/project naar een ander project te brengen. Dit is de standaard, beheerde manier om objecten tussen projecten vrij te geven. Het kan gedaan worden zonder veel uitleg en kan geautomatiseerd \/ gevolgd \/ beheerd worden.<\/P><\/P>Mijn laatste punt betreft de nieuwe versie 10 van MicroStrategy. Aangezien dit het toekomstige rapportageplatform zal zijn, vraag ik me af of er releaseplannen zijn voor EM4MSTR om MSTR 10 te ondersteunen?<\/P><\/P>Met vriendelijke groet<\/P> Christoph<\/P><\/BODY><\/HTML>
Mijn laatste punt betreft de nieuwe versie 10 van MicroStrategy. Aangezien dit het toekomstige rapportageplatform zal zijn, vraag ik me af of er releaseplannen zijn voor EM4MSTR om MSTR 10 te ondersteunen?<\/P>
Met vriendelijke groet<\/P>
Christoph<\/P><\/BODY><\/HTML>
Hi Chaka
Just wanted to check if there are any recent development for this plug-in?
Kind regards
Christoph
Thanks for the reply. You are right, the issues with TX services do not appear anymore with 2.0.1. Also as you said, the newest version works in 10.1. Yes, please keep me posted as we would be more than happy if we could use the plug-in in Visual Insight.
Hi Christoph,
If you are having this issue please contact support, this sounds like an issue that was reported for Esri Maps for MicroStrategy v2.0 and fixed in a patch as well as in the latest release v2.0.1. Please contact support they will be able to help you with this issue.
Our last release of Esri Maps for MicroStrategy v2.0.1 does support MicroStrategy 10, but we are currently working on improving the support in MicroStrategy 10, there are some bugs that we are working on resolving, that will be available in the next release which we hope will be available soon, I do not have an official ETA for this release I will keep you posted.
Cheers
Chaka
Thank you for reply, Chaka
What do you mean by "Our next release will be a localized release that ... "? What means localized in this context? Do you already have an ETA when the next release supporting MSTR 10 will be available?
Chaka, we found a much more serious issue in the meantime. We have a few Transaction Services reports in our project (i.e., reports with data write-back functionality). These reports run in Express Mode. For some reason, whatsoever, they don't work anymore when the Esri plug-in is installed. We were not able to find the reasons for that but we are pretty sure it's because of the plug-in. As soon as we un-deployed it from web the TX reports worked again as expected. Unfortunately this means that we are not able to use / test the plug-in until those bugs are investigated and solve.
Regards
Thanks for the review, Christoph.
I just wanted make a few points that may be helpful based on your review. Location Architect is only fully functional in reports (i.e. dynamically responsive based on the report dataset). Once this report is created with the visualization enabled, an autogenerated map is created based on the Location Architect configurations. Saving this report and exporting it into a new document allows the autogenerated map to be visible in the document, and can be used to create an interactive dashboard without having to reconfigure or style the map. In documents, the autogenerated maps are no longer dynamic based on the contents of the dataset.
The Location architect model is stored in the extended properties of the project. These properties are not easily exportable in MicroStrategy's Object Manager, therefore the example shown in the video is the simplest example. We have future plans to include an improved export mechanism for Location Architect models.
With the recent release of MicroStrategy 10, we do have plans to improve support in other operating modes in Microstrategy Web. Our next release will be a localized release that will have some of these improvements specifically targeting performance in Express/Presentation Mode.
Aangemelde leden kunnen berichten plaatsen, updates volgen en meer. Nieuw hier? Registreer een gratis account.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
.png){kind=avatar}