All posts by Senthilraj

About Senthilraj

DW BI Architect and BI Project Management (Specialized in MicroStrategy). Hobbies/Passion about photography, tennis, music, travel-trekking. Website:

Bursting is a feature in MicroStrategy Distribution Services 9.3 that generates page-by slices and stores results to separate files via subscriptions

Reports and Report Services Documents can use the bursting feature if they are using page-by view filters, and files produced with bursting can use macros to generate unique, individual file names.

  1. Choose a suitable Report or Report Services Document and create a new subscription
  2. Under the “File” heading, select “Add file subscription”
  3. Directly under “File Name” click the button labeled “Burst…”

4.The selector boxes will show the Page-By attributes in the left box.  Move attribute from the “Available” box to the “Selected” box to burst according to those attributes.  Selected Attributes will show in the bar above the selector


5. The file name can be defined in the File Name blank using the following shortcuts:

  • Bursting Attribute: {[Attribute Name]@[Attribute Form]}
  • Date: %%Date%% or {&Date}
  • Time: %%Time%% or {&Time}
  • Recipient Name: %%RecipientName%% or {&RecipientName}
  • User Login: {&UserLogin}
  • Subscription Name: {&Subscription}
  • Project Name: {&Project}
  • Prompt N: {&Prompt#&}
  • Content Name: {&ContentName}
  • Content Details: {&ContentDetails}

6. After filling in the remaining required File Subscription options, click OK to accept these options

MicroStrategy 9.3 What’s New

    1. Tools called MicroStrategy System Manager and System Manager, which can “flow chart” job of Command Manager, Object Manager, Architect and Windows components. Personally very excited to get my hands on this.
    2. Search has feature suggestion like Google search. nah.. not that excited. I know what I do but good for people with bad memory.
    3. Reports can be subscribed to emails/DLs not stored in the metadata (currently it requires). Need to check, but expect a late reply on this.
    4. Different users would get different copy of same file in same location using a better slicing logic.
    5. File import from w/o ODBC driver, LAN locations. Direct import of cross tab excels files. Fire up your visualization.
    6. Data mach-up/selection during file import. Pretty good. :)
    7. Testing of multipass SQL. For developers, this feature would help a lot in troubleshooting the reports. Wow.
    8. More integrated to R, best statistical model programming language.
    9. Crap feature called “Derive metric” available in Visual Insight too. This feature makes BA waste their time in “Self serviced BI”.
    10. Synchronized drilling in dashboard. Pretty good. My current client was expecting this to accomplish this in current MicroStrategy.
    11. Ability to export potion of dashboard instead of whole.
    12. Ability to save personalized view of Dashboard. Business user will ove this, as different users create copies of same report for their connivance of view.
    13. Native connector for Apache Hadoop.
    14. SAP HANA supported minus Partition Tables.
    15. For first time, Multi pass SQL will execute in parallel. But looks like this is good only for multi source reports.
    16. Bloody cool feature of MicroStrategy Health but they will not advise/advertise this. IF you are a MicroStrategy customer, you must use it. Free and excellent feature to track your MicroStrategy implementation.
    17. Better data valiation in Transaction Services. Very select few client for this feature. No word from MicroStrategy on this if same would work from iDevices.
    18. Passing prompt answers between dashboard. I believe this feature was already available. Old wine in new bottle.

Feature missing

  1. Transformation Prompt is under pipeline for last SIX years.
  2. Metric creation/manipulation in MicroStrategy Web was highly expected in this build itself. May be another year.

MicroStrategy Object Manager Package

Open Object Manager –>  Tools –> Create Package


Click on ADD button and choose the objects as shown below

Select the objects either by search results or by selecting folder or by selecting objects

User Action


Use existing No change is made to the destination object.  The source object is not copied.
Replace The destination object is replaced with the
source object.

Note the following:

  • If the conflict type is Exists identically except for path or Exists identically except for Distribution Services objects, the destination object is updated to reflect the path or Distribution Services addresses and contacts of the source object.
  • Replace moves the object into the same parent folder as source object. If the parent path is the same between source and destination but the grandparent path is different, Replace may appear to do nothing because Replace puts the object into the same parent path.
  • Non-empty folders in the destination location will never have the same version ID and modification time as the source, because the folder is copied first and the child objects are added to it, thus changing the version ID and modification times during the copy process.
Keep both No change is made to the destination object. The source object is duplicated in the destination location.
Use newer If the source object’s modification time is  more recent than the destination object’s, the Replace action is used.

Otherwise, the Use existing action is used.

Use older If the source object’s modification time is more recent than the destination object’s, the Use existing action is
used. Otherwise, the Replace action is used.
Merge (user/ group
The privileges, security roles, groups, and Distribution Services addresses and contacts of the source user or group are
added to those of the destination user or group.
Do not move (table
The selected table is not created in the  project. This option is only available if the Allow to override table creation
for non-lookup tables that exist only at source project
.Click Proceed to continue and it shows the following once the package created.

Click Proceed to continue and it shows the following once the package created


Importing a MicroStrategy Object Manager Package:

When you import an update package, you have the option of creating an undo package at the same time as the import. Alternately, you can choose to create an undo package without importing the associated update package.


You import an undo package in the same way as you import any update package. When you import an undo package, the Version ID and Modification Date of all objects in the undo package are restored to their values before the original update package was imported.

Version Control:

Select the Generate log only check box to create a log file describing the changes that would be made if the update package were imported, instead of importing the update package. Select the Save import package XML check box to create an XML file containing instructions for how to import the package, instead of importing the update package. Click Proceed to import the update package, or to create the specified supplemental files.


Edit pane

In the Edit pane of the Import Package or Import Configuration Package dialog box, you can make changes to an update package.

The Edit pane lists the contents of the update package in the following columns:

  • Definition Rule: The conflict resolution rule that is applied to this object. To change the definition rule for an object, click in this column and select a new rule from the drop-down list.
  • Name: The name of the object.
  • Destination folder: The folder in the destination project that the object is copied into.
  • Rename: The name of the object in the destination project. To change this name, click in this column and type the new name for the object.

Schema update options and ACL options for this update package.

Configuring the access control lists for copied objects

When you update or add an object in the destination project, by default the object keeps its access control list (ACL) from the source project. You can change this behavior in two ways:

  • If you resolve a conflict with the Replace action, and the access control lists (ACL) of the objects are different between the two projects, you can choose whether to keep the existing ACL in the destination project or replace it with the ACL from the source project.
  • If you add a new object to the destination project with the Create New or Keep Both action, you can choose to have the object inherit its ACL from the destination folder instead of keeping its own ACL. This is helpful when copying an object into a user’s profile folder, so that the user can have full control over the object.

Note: The Use Older or Use Newer actions always keep the ACL of whichever object (source or destination) is used.

These actions are also used as the default for the ACL options when creating a project update package or a configuration update package.

After successful migration