What functionality is contained in
MicroStrategy Administrator - Object Manager 7.x and 8.0.x?
MicroStrategy
Administrator - Object Manager allows users to perform the following actions:
•
Duplicate and upgrade projects
• Copy
objects within and across related projects
• Move
objects within a project
•
Delete objects within a project
•
Rename objects within a project
•
Search for objects within a project
• Find
an object's parents or children within a project
Are there any special requirements needed to
move objects across projects?
Yes. In
order to perform cross-project operations, the projects involved must originate
from the same source project. In other words, the projects can only be related
by the duplication of a single project. This ensures that the projects have a
similar set of schema and application objects, and that the object ID's in the
two projects are the same. MicroStrategy Object Manager uses the object and
version ID's across the projects to perform comparisons. MicroStrategy Object
Manager
prevents the user from attempting operations across unrelated projects.
How does MicroStrategy Object Manager
determine if two projects are related?
MicroStrategy
Object Manager compares the Schema ID's of the two projects. Duplicated
projects have different Project ID's, but their Schema ID's are the same.
What happens if a user tries to move objects
between two unrelated projects?
If a
user tries to perform cross-project operations between two unrelated projects,
MicroStrategy Object Manager will not permit the operation and will display the
following error:
Objects cannot be copied across the projects because these two
projects, "Project name of the source" and "Project name of the
destination", have not been created from the same source. For more
information see Chapter 4: Managing Your Applications, in the System
Administration Guide.
What is the Conflict Resolution Window?
The
Conflict Resolution window provides the user with a means to decide how to
handle object conflicts between the source project and the destination project.
In addition, the Conflict Resolution window displays the object name in the
original project, the object name in the destination project and the type of
conflict. Users may also specify a new name for the object depending on the
action chosen.
How does MicroStrategy Object Manager
determine if two objects in different projects are the same?
To
determine if two objects are the same, MicroStrategy Object Manager compares
their Object ID's. If these ID's are the same, MicroStrategy Object Manager
then compares the Version ID's. If the Version ID's are the same, the Conflict
Resolution grid lists the conflict as 'Exists Identically.' If the Version ID's
are different, the Conflict Resolution grid lists the conflict as 'Exists
Differently.'
How can the user determine the Object ID of an
object?
To view
the Object ID of an object, right-mouse click on the object and select
'Properties.' The Object ID and Version ID are listed on the 'General' tab.
Why does MicroStrategy Object Manager search
for object dependencies?
MicroStrategy
Object Manager makes a list of all object dependencies before copying an object
to prevent metadata inconsistency. The time required for dependency checking
varies based on a customer's metadata size and schema complexity. For large
metadata and complex schemas, gathering all the dependencies may take a long
time.
Can schema objects be copied across projects
with MicroStrategy Object Manager?
Yes,
schema objects can be copied across projects using MicroStrategy Object
Manager. 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. However, subtle changes in the warehouse that relate to
prefixes, views, or table structure cannot be tracked by MicroStrategy Object
Manager. For situations where the projects' warehouse structures or setups are
dissimilar, users may be required to make further edits of the objects to
ensure full integration into the destination project. These edits may include
hierarchical relationship changes or modifications to the prefixes.
How does MicroStrategy Object Manager
integrate with the MicroStrategy Product Suite security model?
Security
in MicroStrategy Object Manager is based on the MicroStrategy 7.x Product Suite
security model. All activities that can be performed in MicroStrategy Object
Manager are governed by privileges and access control lists. For example, if a
user is not allowed to access a certain folder in MicroStrategy Agent, they
will not be able to access the folder in MicroStrategy Object Manager.
No comments:
Post a Comment