CAUSE: This is a known issue with MicroStrategy 10. 0. MicroStrategy projects contain schemas and related schema objects, including attributes, tables, hierarchies, and so on. The system hierarchy is the default hierarchy that MicroStrategy sets up for you each time you create a project. Facts, attributes, hierarchies, and other schema objects are the building blocks for application objects such as reports and documents. 1 MicroStrategy Hierarchies are Schema Objects made of Attributes, which serve two main purposes: Browse Library. Hierarchies − They represent the relationship between various attribute values. Schema objects directly reflect the warehouse structure and include attributes, facts, functions, hierarchies, operators, partition. Explanation: In MicroStrategy, a schema object is an object that defines the structure of a database or data warehouse. Create Relationships in System HierarchiesAn object is a basic building block in MicroStrategy. Explanation: A hierarchy in MicroStrategy is a set of related attributes arranged in a tree-like structure. LOGICAL_SIZE]) #. This setting has four values:They can import the tables or define the query to pull the data into the schema, define the attributes and facts that will be the basis for other objects, and establish relationships and cardinality between attributes by creating hierarchies. Controlling access to data at the database (RDBMS) level. "System Prompt" is a system object that was introduced back in version 8. Application. Drag the Test Hierarchy into the Data Explorer folder. Stitching is based on the full path of objects with the following structure: (system) > database > schema > table > column. System Hierarchy. Creating application objects and Schema to serve the user communities of both Web and MicroStrategy Desktop. Therefore, unlike the Schema Objects, it is not necessary to perform an update schema after any Public. Your building blocks – Schema Objects; The Source – Tables; Business raw measures – Facts; Business context – Attributes; Grouping business context – Hierarchies;This update is required when you make any changes to schema objects such as facts, attributes, or hierarchies. Error(s) occurred while loading schema: DSSSQLEngine: Schema loading error: Population Exception: The object shown in the following hierarchy no longer exists in the schema: -Dimension/Hierarchy-Attribute:Object is not found in DFCSchema during DFC conversion Error(s) occurred while loading schema: 0. Looking for MicroStrategy Interview Questions to Getting? We possess an ULTIMATE Guide of knowledge-Based ️Market Trend Featured ️100% Success ️PRO-Tips | Hand UP!!Read Only: Read only mode allows you to view the schema objects without locking the schema from other users. "System Prompt" is a system object that was introduced back in version 8. User. If you open a schema editor in read only mode, the entire project is enabled to use read only mode. Browse Library Advanced Search Sign. Schema objects include facts, hierarchies, and custom groups; application objects include reports, documents, and metrics; and configuration objects include project sources, database instances. Schema objects. The key will show up on the screen and will. Login to MicroStrategy developer as administrator. An object is a basic building block in MicroStrategy. Create Relationships in System Hierarchies Considerations for the use of star schemas with MicroStrategy SQL Generation. With these MicroStrategy objects, you will enhance and scale your BI and Analytics solutions. The project schema refers to an internal map that MicroStrategy uses to keep track of attribute relationships, fact levels, table sizes, and so on within a project. Navigate to MicroStrategy Tutorial and expand the Schema Objects option. MicroStrategy Schema Modeling With the modeling tool, architects can map the physical database schema, model data based on business requirements and terminology, and build complex hierarchies to organize data and better reflect relationships. Created all possible Metrics, for enabling the end users to generate customized reports by creating their own Templates and Filters, Administrated MicroStrategy Intelligence Server and Web Server. A solution is offered. A continuación se muestran los distintos objetos de esquema con su descripción. An object used to provide analysis of and insight into relevant data. When the system hierarchy is displayed, the background of the viewer is grey. Microstrategy Document Editor Sections Important Notes: The Layout area is in the center of the Document Editor interface and provides the framework for precisely controlling where controls (such as text fields, grid and graph reports, images, and widgets) are displayed when the document is viewed in different display modes, printed,. Create a Report Services Document. CAUSE: This is a known issue in MicroStrategy Web 9. A user group (or "group" for short) is a collection of users and/or subgroups. Browse Library Advanced Search Sign. Error(s) occurred while loading schema: 0This tutorial is the second part of the complete overview of the preparation of the MicroStrategy 9 environment, from setting up the Intelligence Server to go live on Web. 0. LU_. Hierarchy Reporting with Ragged Hierarchies; Filtering for a Level Metric;. The Modeling service is a microservice that enables MicroStrategy users to create and manage application and schema objects through Workstation. ” The schema tables do not need to correlate on a one-to-one basis with the abstraction tables, and may combine information from different abstraction tables. MicroStrategy Workstation allows you to browse and search for schema objects. A system hierarchy is maintained by the relationships that exist among the project’s schema objects. x create a new report. There is a good explanation on how to overcome those issues. Cards can be consumed in a web browser via the MicroStrategy HyperIntelligence Chrome extension and on iOS devices via the MicroStrategy. This process reloads the internal representation so that it matches the definitions of. Schema objects include facts, hierarchies, and custom groups; application objects include reports, documents, and metrics; and configuration objects include project sources, database instances. In the Schema Update dialog box, select or clear the following check boxes: Update schema logical information: Use this option if you added, modified, or deleted a schema object. The object is named as "User. In MicroStrategy Developer, log into the project source that contains your project and open the project. The objects you can create in MicroStrategy Developer fall into one of three groups: schema objects, application objects, and reports and documents. The object is named as "User Login" and is implemented as a prompt object. Scan MD. However, there are MDX cube source objects that can be manipulated in ways that affect how their related MicroStrategy objects are defined: Dimensions in MDX cube sources are not directly mapped to MicroStrategy objects. Open the Workstation window with the Navigation pane in smart mode. In the example above, the two airport attributes do not have a common. Some of these options are available in the MicroStrategy Architect Settings dialog box. The attribute might have system managed objects that depend on it, that are not directly visible to the user. The object hierarchy does not record data related to configuration objects (subscriptions, schedules, users, user. The options you can define determine how Architect displays data, automatically creates and maps schema objects, loads the Warehouse Catalog, and updates the project's schema. The object is named as "User Login" and is implemented as a prompt object. . Business Intelligence with MicroStrategy Cookbook. Perform multiple layers of dependency searches on schema objects to find application objects that use them . Use the Warehouse Catalog to move and update tables in Microstrategy. 0. Responsible for designing and executing Application objects and Schema objects using MicroStrategy Desktop. 0. List of the metadata repositories that contain the configuration, schema, and application objects being monitored by Platform Analytics. This KB article discusses an issue that may occur when updating Schema in MicroStrategy Developer 9. Lookup tables are usually. Relationship Tables. 0. User-defined hierarchies do not need to follow the logical data model and can be modified to include additional attributes or limit user access to them. Through these interview questions and answers you will learn what is metadata, attributes, mapping, hierarchies, facts, smart metrics, transformations, filters, prompts and more. That is to say, it will be easiest to model your objects in the tool with the schema designed in this manner. Transformation - Logical objects used to compare values at different times. Worked with data modeling team on the dimension model to close out the gaps in the model to best use the underlying tables needed for BI layer. MicroStrategy Hierarchies are Schema Objects made of Attributes, which serve two main purposes: Help to visualize and understand the relationships between the Attributes; Define paths for users to drill (drill maps and drill paths) The following is a quick reference table for this MicroStrategy Object:Facts, attributes, and hierarchies are examples of schema objects. This video showcases the end-to-end workflows for admins and architects supported in Workstation with 2021 Update 2. They help in carrying out drill-up and drill-down. This information includes metric and attribute counts, information on hierarchies and transformations, and whether a given schema is locked or unlocked. Hierarchies are groupings of attributes that can be displayed, either ordered or unordered, to reflect the relationships that exist between the attributes in a project. Attributes, facts, functions, and operations, hierarchies, partition mappings, tables, and transformations are all schema objects; however, three schema objects comprise the core of project definition and will be. If the document or layout is grouped, the groups are displayed in the drop-down list. Error(s) occurred while loading schema: DSSSQLEngine: Schema loading error: Population Exception: The object shown in the following hierarchy no longer exists in schema: -Link-TableObject is not found in DFCSchema during DFC conversion. Schema objects: Schema objects are generally created by a project designer and include such things as facts, attributes, hierarchies, and transformations. 2, 9. A project also represents the intersection of a data source, metadata repository, and user community. For example, a Time dimension in a star schema may be supported by a dimension table with the following structure: DAY_ID. Drilling using hierarchies. All of the schema objects—facts, attributes, hierarchies, transformations, and so on—in your project come together to form your project's schema. As Ugur says, MSTR is quite capable of working with a star schema, and depending on your data, it may be better to use a star schema (for performance purposes) even if the modelling is a little (or a lot) harder in the. Though the Region_id and Reg_id columns have different names, they store the same data: information about regions. User-defined hierarchies do not need to follow the logical data model and can be modified to include additional attributes or limit user access to them. A search for dependent objects shows only logical table and system hierarchies that should not prevent an attribute to be deleted. hierarchy even though they are in different dimensions in the data warehouse. 0. Hover over the user-defined hierarchy you want to rename. This platform supports various types of scorecards, interactive dashboards, and automated reports. Labels: #Recursive hierarchies microstrategy #Recursive Hierarchy. The logical table from the development project will be copied to the production project as a dependent. MicroStrategy. Create a filter on the attribute "Year. You can get the ID by navigating to the cube or report within MicroStrategy Web, right-clicking on the desired cube, and selecting Properties. The modeling tool allows architects to transform a complex enterprise data environment into a unified. ) that can be reused across projects, reports, dashboards, and applications. but the attribute relationship in the MicroStrategy schema is defined. The Object hierarchy and fact tables track all key schema (tables, facts, attributes, etc) and application objects (reports, dashboard, cubes, etc) stored in the MicroStrategy Metadata(s) being monitored by Platform Analytics. Create Relationships in System HierarchiesConsiderations for the use of star schemas with MicroStrategy SQL Generation. Thanks to MicroStrategy Semantic Graph it is possible to analyze parent-child relations between objects. In the MicroStrategy 2020 Update 2 release, users can create and manage standalone filters using the Filter Editor accessed from the main Workstation window. They typically consist of descriptions of dimensions. CONTENTS 1. Schema objects:. Firstly populate the metadata with project definition and schema objects. 2. STEPS TO REPRODUCE: Create a document in MicroStrategy Developer or Web 10. Rather, the project schema refers to an. Click the icon and enter the new name. This hierarchy is specifically created for report designers. 0 and the 4. Star schemas are supported with restrictions, as long as fact tables are not at a higher level than the dimension tables to which they are joined. Create an empty MD shell in Microsoft Access. The object can be found under Public Objects > Prompts > System prompts, as shown below: Unlike ordinary prompt objects, system prompts don't require any answers from the user. The menu should look like this: But the menu will be missing objects and will look like this:By learning about objects and different object types, you will develop a strong understanding of the MicroStrategy Schema and Public Objects. Packages API The Packages API family allows you to create and import migration packages. Error(s) occurred while loading schema: 9. "System Prompt" is a system object that was introduced back in version 8. Recalculate table keys and fact entry levels: Use this option if. The auto-generated numeric ID for. This hierarchy is specifically created for report designers. Update the data on an Intelligent Cube without having to republish the entire cube in MicroStrategy MicroStrategy has introduced a feature known as, Incremental Refresh Options, which allow Intelligent Cubes to be updated based on one or more attributes, by setting up incremental refresh settings to update the Intelligent Cube with. 4. Business Objects, S. Traditionally, hierarchies within the MicroStrategy platform are modeled with fixed tables, categories and levels, which can often be limiting due to dynamic real-world. On the next screen, select the DSI you want, then click the Generate Geospatial Service key button. x with any number of attributes. Place attributes Country and Distribution Center on report template, and the above metric either on report template, or in Report Objects window if you have an OLAP license. When the system hierarchy is displayed, the background of the viewer is grey. The object can be found under Public Objects > Prompts > System prompts, as shown below: Unlike ordinary prompt objects, system prompts don't require any answers from the user. Update the data on an Intelligent Cube without having to republish the entire cube in MicroStrategy. Maintain MicroStrategy schema objects and public objects. Recursive Hierarchies. KB45087: "[DFCSCHEMA] Population Exception: The object shown in the following hierarchy no longer exists in schema: -Dimension/Hierarchy-Attribute Form. 4. These attributes and facts are part of the report definition that the MicroStrategy Engine refers to when a report. User-defined hierarchies do not need to follow the logical data model and can be modified to include additional attributes or limit user access to them. While, Public objects are used to create other. 2. Certain MicroStrategy features automatically create new schema objects, referred to as managed objects, which are not directly related to the project schema. Drilling is a function in MicroStrategy reports that allows. 0. For more information on what a logical data model is and how to create one, see The Logical. This means that every schema editor automatically opens in read only mode. MicroStrategy introduced HyperCards, a new object that is built, managed, and deployed using MicroStrategy Workstation(Not by using Developer or Desktop as far as I know). We determination cover Technical, Attributes, Schema, Project Creation is few product. ) and public objects (metrics, filters, templates, reports, dashboards, etc. MicroStrategy Architect is a project design tool, which allows you to define all the required components of your project from a centralized interface. This hierarchy is specifically created for report designers. In MicroStrategy Desktop 9. The object can be found under Public Objects > Prompts > System prompts, as shown below: Unlike ordinary prompt objects, system prompts don't require any answers from the user. ) as well as MicroStrategy application objects (Metrics, Filters, Templates, etc. This course will make you walk through the essentials of MicroStrategy and its architecture, create schema objects, project design, and many. In the right corner of the dashboard, change the data source to none. Create Relationships in System HierarchiesMicroStrategy Hierarchies are Schema Objects made of Attributes, which serve two main purposes:. x and 10. Therefore, unlike the Schema Objects, it is not necessary to perform an update schema after any Public. Hierarchies; Comparing data across time – Transformations;. 4. x. Make two grids with different attributes and metrics in each. 4. Update schema. The Modeling service is a new microservice that enables MicroStrategy users to create and manage application and schema objects through Workstation. Make a shortcut to the Test Hierarchy in the Schema Objects > Hierarchies folder. Used MicroStrategy Desktop 9. Error(s) occurred while loading schema: DSSSQLEngine: Schema loading error: Population Exception: The object shown in the following hierarchy no longer exists in schema: -RoleObject is not found in DFCSchema during DFC conversion. Lookup tables are usually joined to fact tables to group the numeric facts in the fact table by dimensional attributes in the lookup tables. For steps to access this dialog box, see Accessing the Architect options. Error(s) occurred while loading Schema DSSSQLEngine: Schema loading error: Population Exceptions: The object shown in the following hierarchy no longer exists in schema: Relation-Table The object definition is incomplete or inconsistent. Right-click on the metric header to apply the condition or threshold and select 'Alerts': Specify the conditions to meet for the delivery to be triggered in the filter editor: Expand the Delivery Settings section. Click the icon and enter the new name. Users can also create compound attributes, define attribute relationships in the system hierarchy and modify display and sort. Application Objects: Also known as Public Objects, these objects represent reporting and visualization objects. In the left pane, click Available to view all attributes that can be added to the user-defined hierarchy. Watch video to learn how MicroStrategy schema modeling works. Hierarchies, Prompts, Filters etc. reload(update_types=[SchemaUpdateType. Ragged Hierarchies in Microstrategy. This is because they are only necessary with ragged/unbalanced hierarchies which are not supported as null attribute IDs are not. Click User Defined Hierarchy at the top of the Hierarchy Editor and choose the target hierarchy. The options you can define determine how Architect displays data, automatically creates and maps schema objects, loads the Warehouse Catalog, and updates the project's schema. Drag the Test Hierarchy into the Data Explorer folder. MSTR has evolved dashboards to the point that they are more than dashboards - they are interactive, collaborative analytic stories . Although the concepts are related, the project schema is not the same as the physical warehouse schema. Schema objects include facts, hierarchies, and custom groups; application objects include reports, documents, and metrics; and configuration objects include project sources, database instances. A variety of objects are classified as managed objects, including all Freeform SQL objects. Rather, the project schema refers to an. This hierarchy is specifically created for report designers. Update schema. Once the target hierarchy is opened, you can start editing it. If you open a schema editor in read only mode, the entire project is enabled to use read only mode. The option to Delete unused managed objects allows a MSTR Admin to force a search and delete of those managed objects which no longer are in use by the project (no longer have dependants). Logical tables are MicroStrategy objects that form the foundation of a schema. Certain MicroStrategy features automatically create new schema objects, referred to as managed objects, which are not directly related to the project schema. Ragged Hierarchies Chapter 5: Leveraging advanced data warehouse schema design Chapter 6: Using logical views to map schema objects to SQL queries Chapter 7: Resolving many-to-many attribute relationships Chapter 8: Specifying attribute roles Chapter 9: Implementing hierarchies with data modeling techniques Chapter 10: Managing slowly changing dimensions. Interact with the engaged MicroStrategy Community to get answers to all your questions and collaborate for solutions. an information about an object representing a child in a current hierarchy relationship, SchemaObjectReference object class mstrio. When a new attribute is added to a hierarchy, the attribute by default will not show up in the MicroStrategy Developer Data Explorer side bar. Do not use this option if the configuration file contains an instruction to update the schema. 0. The attribute editor allows users to create attribute forms, connect attributes to logical tables in the schema, and edit form expressions. Application object: Reports, filters, documents, templates, metrics, prompts, custom groups are. If projects are distributed asymmetrically across the cluster, when you assign an event-triggered schedule to a project, make sure you trigger the event on all nodes on which that project is loaded. Make a shortcut to the Test Hierarchy in the Schema Objects > Hierarchies folder. From the File menu, select New, and then Hierarchy. the project schema refers to an internal map that MicroStrategy uses to keep track of attribute relationships, fact levels, table sizes, and so on within the project. Physical tables in a data warehouse consist of columns, and logical tables in the MicroStrategy schema relate this column data to attributes and facts. This is an integrated object in MicroStrategy that connects to source databases. For an introduction to user hierarchies and system hierarchies, see Types of. MicroStrategy Object Manager moves objects seamlessly between similar projects such as from a development project version to a production project version where the warehouses are the same in terms of views, prefixes, and warehouse structure. Follow the steps below to create a list of all groups and the users in each group: In MicroStrategy Developer 9. Remove any table object with the type of +. Map schema objects to new tables automatically: Select to map schema objects automatically to new tables. Specify to skip importing creation data, modification date, and author for schema objects. Application Objects : Which are built using schema objects. Click the icon and enter the new name. Recommendation. It is the primary contact layer between. With these MicroStrategy objects, you will enhance and scale your BI and Analytics solutions. Run Repository Translation Wizard from the Start Menu -> Programs -> MicroStrategy-> Object Manager. Edit an Existing User-Defined Hierarchy. User-Defined Hierarchy. User-defined hierarchies do not need to follow the logical data model and can be modified to include additional attributes or limit user access to them. To delete a hierarchy from the list, select the hierarchy and click Remove. Notice that a joint child relationship can be one-to-many or many-to-many. The user hierarchy is a hierarchy which you create specifically for your report designers. As the name suggests, these objects are used by the users and analysts (Public), and the. Schema objects include facts, attributes, hierarchies, and other objects which are stored in the Schema Objects folder in MicroStrategy Developer's folder list. Schema objects—Objects that are created in the application to correspond to database objects, such as tables, views, and columns. Architects can also create multiple objects to tailor the content for the end-users. Hierarchies Logical objects that enable you to group attributes to reflect their relationships or provide convenient browsing and drilling paths in the MicroStrategy reporting environment. • Maintenance of MicroStrategy projects. The drilling option between attributes and between different levels of an attribute in a hierarchy depends on teh relation we setup in the microstrategy architect. The impact is limited to cases when logical tables are inadvertently deleted from the schema collection. Connect to your environment (s). If the issue persists, please contact MicroStrategy Technical Support for further assistance. Hierarchy Reporting with Ragged Hierarchies; Filtering for a Level Metric;. , Attributes, Facts, Hierarchies, partition mappings, Tables or Transformation). x, select 'Project Documentation' from the Tools menu to start the wizard. Error(s) occured while loading schema:1. 3. Schema objects include facts, hierarchies, and custom groups; project objects include reports, documents, and metrics; and configuration objects include project sources, database instances, and users. a lookup table. Logical tables are MicroStrategy objects that form the foundation of a schema. 4. All of the schema objects—facts, attributes, hierarchies, transformations, and so on—in your project come together to form your project's schema. However, you cannot make any changes to the schema object. To remove all the hierarchies from the list, click Clear. The logical data model is composed of data abstraction objects (attributes, dimensions, etc. Numeric prompt: Users enter a specific number, up to 15 digits, which is then used as part of a filter, or within a metric, to look for specific numeric data. • Designing and developing BI solutions based on MicroStrategy platform. With these MicroStrategy objects, you will enhance and scale your BI and Analytics solutions. Se abre la siguiente pantalla mostrando los distintos objetos de esquema. Update schema logical information: The MicroStrategy SQL Generation Engine uses an internal representation of the project's schema, which is held in MicroStrategy Intelligence Server memory (or MicroStrategy Developer memory, in two-tier connections). The lu_component_object tables are views on the underlying lu_object tables. Select the Members tab. x/8. Hierarchies Logical objects that enable you to group attributes to reflect their related or provide convenient browsing both drilling paths in the MicroStrategy reporting environment. These are MicroStrategy specific objects eg : Metrics, FIlter, Reports etc 3. #Recursive hierarchies. Developed Complex business reports in desktop using multiple Prompts, Filters and Compound metrics. The schema objects can then be seen in Desktop in the users Profile folder or in Public Objects. The Scan MD tool executes tests to detect inconsistencies in the metadata. On the left, under Layout Properties, select Advanced. 1 to build schema objects Hierarchies, Transformations, Attributes, Facts and Relationships as a function of the logical model. 2. Create Relationships in System Hierarchies MicroStrategy Hierarchies are Schema Objects made of Attributes, which serve two main purposes: Browse Library. facts, attributes, hierarchies, aggregation, and portal integration. "System Prompt" is a system object that was introduced back in version 8. The system hierarchy is automatically created when you create a project and is maintained by the relationships that exist among the project's schema objects. The MicroStrategy Tutorial project uses aggregate tables by default. A project also represents the intersection of a data source, metadata repository, and user community. Lookup Tables. From the Fetch Level drop-down list, select the object to be counted for the incremental fetch level. Drop Files. The different kinds of value prompts are: Date prompt: Users enter a specific date for which to see data. 1, 9. In The Logical Data Model, you learned how to use hierarchies to group related attributes in practical. NET Framework 4. 0. User-Defined Hierarchy. The two types of hierarchies that exist in MicroStrategy include: System hierarchy: The system hierarchy is created according to the relationships defined between the. User-Defined Hierarchy. However, you cannot make any changes to the schema object. However, to make a user hierarchy available for browsing in the Data Explorer you must place it in the Data Explorer folder—a subfolder of the Hierarchies folder, which is located in the Schema Objects folder. KB429013: "The object shown in the following hierarchy no longer exists in schema: -Relation-TableObject is not found in D… Number of Views 1. Print Project Schema opens the Print Project Schema dialog box, on which you can request printing of schema connections, warehouse tables, fact and attribute definitions, physical or logical table-catalog views. Facts - Son los valores numéricos, que se. x, select 'Project Documentation' from the Tools menu to start the wizard. You can sort, filter, search by name and ID, and change security access for schema objects,. Select the users or groups that you want to add to the object's ACL. This chapter. They are the bridge between MicroStrategy reporting environment and data warehouse. x. 0. Configuration objects include objects that are used by all projects in a project source, such as users and user groups, database instances and logins, security roles, and Distribution Services devices, transmitters, and. 0. Click User Defined Hierarchy at the top of the Hierarchy Editor and choose the target hierarchy. but the attribute relationship in the MicroStrategy schema is defined incorrectly with a one-to-many. User-defined hierarchies do not need to follow the logical data model and can be modified to include additional attributes or limit user access to them. These report objects are discussed in detail in the Advanced Reporting Help. In MicroStrategy Web 9. A project is where you build and store all schema objects and information you need to create application objects such as reports in the MicroStrategy environment, which together provide a flexible reporting environment. Select any project that is in the project source that contains the users and groups and click Next. Browsers automatically handle cookies, but if you are using your own client, you need to. An object is a basic building block in MicroStrategy. hdbprocedure file) or in a database. 0. 0. UserHierarchy ( connection : Connection , id : Optional [ str ] = None , name : Optional [ str ] = None ) ¶Schema objects represent different components of the logical data model and are directly mapped to a column or columns in the database. Describe how user hierarchies are used in a MicroStrategy project create user from TI 1 at Centro Universitário SENAC - SENACSPThe goal is to create an image link that is used to export the grid, like shown below: Document in Edit Mode. Watch video to learn how MicroStrategy schema modeling works. If you have selected to automatically create attributes, attribute forms, and facts based on schema. These types of hierarchies include the system hierarchy and the user hierarchy. In the MicroStrategy 2021 Update 5 release, users can create and manage standalone facts, attributes, user hierarchies, system hierarchy, schema, filters, custom groups, security filters, derived. The Hierarchy Viewer allows users to view both the user-defined hierarchies and the system hierarchy in MicroStrategy Developer 9. 54K. Mastering Business Intelligence with MicroStrategy. The Grouping Properties dialog box opens. Hierarchies; Comparing data across time – Transformations;. However, the levels within a dimension in an MDX cube source are mapped to hierarchies and attributes in MicroStrategy. MicroStrategy recommends you choose Automatic if you are unsure what tables contain the column used in the expression. Objects of this type that can be used in MicroStrategy Web are: Attributes Hierarchies Facts PUBLIC OBJECTS Public objects in the Public Objects folder are created and managed by the Reporting Support team. DAY_DESC. In Developer, Workstation or Web interfaces you can for example check what metrics are built on top of a fact (dependents) or what metrics has been used in report definition (components).