MicroStrategy Object Manager can assist you in managing objects as they travel through the life cycle of your project. You can copy items within a project or across projects with Object Manager. Application, schema, and configuration objects can all be copied using Object Manager.

Every item in the MicroStrategy system has an ID (or GUID) and aversion.

When you use Object Manager to copy objects between projects, a conflict occurs if an object with the same ID as the source object exists elsewhere in the destination project. The Object Manager program assists you in resolving the problem. You can, for example, duplicate an existing object and replace it with a newer object, and so on.

Object definitions, functions, and the fundamentals of MicroStrategy

It is necessary to understand the fundamental ideas underpinning objects and expressions to comprehend functions and their role in MicroStrategy.

In MicroStrategy, an object is a fundamental building block. Objects can be divided into three categories: schema objects, application objects, and configuration objects. Facts, hierarchies, and custom groups are schema items; reports, documents, and metrics are application objects; and project sources, database instances, and users are configuration objects.

Maintaining objects

You are the one who creates, maintains, and deletes MicroStrategy objects. For example, your Architect will construct attributes by translating conceptual data from your data warehouse to names that will display on your reports, such as Month, Customer Name, or Product Category. Your Designer will design metrics that will allow you to access and manipulate numeric data in your data warehouse.

When creating or changing many objects, you must specify an expression. Any character combination that can be employed as a result is referred to as an expression. The following are some examples.

Data warehouse

In the first scenario, each Month element in your data warehouse is given a numeric ID ranging from 1 to 12, with January being 1, February being 2, and so on. You'd want to create a report that includes a five-month projection. One approach is to create a new attribute named 5 Months Ahead and define it with the expression Month + 5 in the attribute specification.

Data expressions

Expressions can be utilized in a variety of situations. Metrics, in particular, frequently necessitate complex expressions. The term Sum(Revenue) is used to establish a reasonably simple statistic in the second example above. “Sum” instructs MicroStrategy to read separate Revenue elements from the data warehouse and combine them into a single number.

Above is an example of a logical expression that could be used in a filter. A filter with the words New York AND Los Angeles would allow a user to answer queries like "Which business travelers flew out of New York and Los Angeles in 2006?"

Expressions are frequently used to create objects, which are the fundamental components of all MicroStrategy content and functionality. Changing the object expressions is a common way to edit objects that rely on these expressions.

Functions

A MicroStrategy function will almost always be used to build an expression that achieves your purpose. MicroStrategy functions are useful tools for defining MicroStrategy objects (when they're included in object definitions) and initiating complicated user-selected calculations. The Sum function is used in the example Sum(Profit) in a metric definition to add several Profit values in a data warehouse to arrive at a single final amount to display on a report.

A function can be used whenever an expression is used. You may use a huge library of functions that come with MicroStrategy to develop custom expressions for everything from creating simple objects to building complicated reports and analyzing data. Although functions are most typically employed in metric expressions, they are also used to build MicroStrategy objects such as attribute forms, consolidation elements, custom groups, filters, facts, subtotals, and transformations.

Objects

MicroStrategy objects are found at the system layer and can be used in a variety of projects. Users, database instances, database login IDs, and schedules are examples of configuration items.

As an administrator, we get the Administration option under MicroStrategy Secure Enterprise when we log in to MicroStrategy Developer. The numerous configuration objects are detailed in the following sections after expanding this option.

Manager of Users

The administrator uses these items to manage MicroStrategy users. It's set up to accommodate the following user preferences. The following setup options are available.

• To allow the user into the environment, the user must first authenticate.

• A user group is a collection of users who have been given a set of privileges.

• User privileges allow users to use only a subset of the environment's features.

• To authorize or prevent the use of a certain object, use user permissions.

Manager of Configuration

These items are used to keep track of database connectivity. They keep track of the paths and credentials for the many databases that MicroStrategy can connect to. The following setup options are available:

• The name of the database instance as well as the credentials for it.

• Connection lifetime This limit specifies the maximum length of time a database connection thread can be cached.

• The tasks associated with a database event are triggered by events.

• The user's access to various database objects is controlled by the security role.

Monitor the system

Many system monitors are available to assist in determining the health of the MicroStrategy environment. They assist in estimating the load on the system as well as any potential performance issues. Some of the most essential system monitoring options are shown here.

• Jobs keeps track of the jobs that are currently running.

• User Connections keeps track of how many users are connected at any given time.

• Caches keep track of how many caches there are and how big they are.

Administration of the system

Setting up numerous projects, allocating clusters to the projects, and scheduling maintenance windows are all part of this administrative task.

Packages from the Object Manager without Locking the MicroStrategy Project

When numerous developers are working in the same environment, project locks are common. When you make a metadata modification, such as adding or modifying attributes, you'll get a project lock. Project locks during Object Manager migrations can be inconvenient due to the many moving aspects of the development life cycle.

Fortunately, creating Object Manager packages without locking the project is possible. It's simple to travel to the location. It's under Preferences > Tool > Object Manager.

Object Manager

 Object Manager will not allow you to migrate or copy a report if the attribute forms of an attribute utilized in the report differ between the source and destination projects.

Workaround: 

To resolve this conflict, seek the properties that conflict with the report's dependencies in the source project. With the Replace action, migrate these characteristics to the destination project. After that, you can move the report.

It's not a good idea to run two instances of Object Manager on the same workstation, especially if they're both tied to the same project. There will be locking conflicts.

Conclusion

Each object in the MicroStrategy architecture is recognized by a unique Object ID. The Object ID is used to control the functioning of the MicroStrategy Object Manager. As a result, items with different names in connected projects with the same Object ID could potentially be related. When an object is copied from one project to another or duplicated as part of a project duplication operation, the name of either object is modified. You can learn more about object managers through MicroStrategy online training.