MicroStrategy allows us to link documents to other documents/reports and create a navigation between them. Depending on our needs, the default way of Microstrategy to make links couldn´t be enough for our purposes, for this reason I will talk about API URL, which allow us to create custom links to other reports, documents, pages, exports … from objects such as text labels or images:
Author: Miguel Pereira
Some time ago I published an entry in relation to the creation of Datamart Report in Microstrategy, which you can find at this link:
Now I will devote a few lines to speak further about configuration and characteristics of this functionality.
MicroStrategy provide us the possibility to store statistics about our projects in physical tables. This information is varied and includes access dates, fault recording, runtimes … If we want to see the definition and composition of statistical tables which Microstrategy gathers, we can consult in:
since 463 page, there, we can see the information contained in each table.
In this post, I will combine information from the statistics repository with the information which we have in MicroStrategy metadata, for this reason it is advisable to take a look at the previous post:
Microstrategy provides us a good utility which we usually not use, insert a custom report DataMart as another table in our model. This is very simple, we need to go the the next menu:
The Microsotrategy Metadata is a repository which stores all the definitions of MicroStrategy objects. We can get an overview of all these objects and their relationships using queries against the tables of this repository.
In internet, the information about MicroStrategy metadata is very scarce , so, I want to share with you some information which I found interesting and queries which could be useful. Although Metedata is composed by multiple tables deeply interrelated , I will highlight four of these which I consider most useful
En las versiones 9.3 y anteriores de Microstrategy, nos encontrábamos con una especie de “bug” visual en Microstrategy Web cuando usábamos atributos cuya representación usaba el carácter ‘*’, sin embargo no afectaba a la hora del cálculo y representación de los datos en un informe.
Esta es una incidencia, ya conocida por Microstrategy, ya solucionada a partir de la versión 9.3. Aquí podemos ver una TN que habla del problema sobre el que os voy a escribir:
TN37702: “1048576” is displayed in prompt detail when answering a prompted Freeform SQL report with attribute ID form element which is end with an asterisk (*) in MicroStrategy Web 9.x
Ilustro el caso más ampliamente para que veáis a que me refiero.