Skip to main content

Bursting file subscriptions Microstartegy

Bursting file subscriptions: Delivering parts of reports across multiple files:

Large MicroStrategy reports and documents are often broken up into separate pages by attributes. In a similar way, with Distribution Services, you can split up, or burst, a report or document into multiple files. When the subscription is executed, a separate file is created for each element of each attribute selected for bursting. Each file has a portion of data according to the attributes used to group data in the report (page-by axis) or document (group-by axis).
Ex:, you may have a report with information for all regions. You could place Region in the page-by axis and burst the file subscription into the separate regions. This creates one report file for each region.

As a second ex:, if you choose to burst your report using the Region and Category attributes, a separate file is created for each combination of Region and Category, such as Central and Books as a report, Central and Electronics as another, and so on.
When creating the subscription for PDF, Excel, plain text, and CSV file formats, you can use macros to ensure that each file has a unique name. For example, if you choose to burst your document using the Region and Category attributes, you can provide {[Region]@[DESC]}, {[Category]@[DESC]} as the file name. When the subscription is executed, each file name begins with the names of the attribute elements used to generate the file, such as Central, Books or Central, Electronics.

To burst a file subscription across multiple files

1Create a file subscription in MicroStrategy Web.
2In the Subscription Editor, click Burst… The Select Bursting Criteria options are displayed. All attributes used to group data in the report or document are shown in the Available Attributes list.
3From the Available Attributes list, select the attributes to use to break up the data, then click the right arrow to move those attributes to the Selected Attributes list.
4To change the order of attributes for bursting, select an attribute in the Selected Attributes list, then click the up or down arrow.
5In the File Name field, type a name for the burst files. You can use macros to ensure that each file has a unique name.
6Click OK to save the subscription.

Delivering parts of reports across multiple files: Bursting file subscriptions to subfolders

Large MicroStrategy reports and documents can be divided into separate pages by attributes. In a similar way with Distribution Services, you can break, or burst, a report or document into multiple subfolders, with each subfolder containing report or document with a portion of data divided by the attributes in the report’s page-by or the document’s group-by axis. When the subscription is executed, subfolders are dynamically created, if they do not already exist, with the names of the attribute elements. To do this, you provide macro text as part of the bursting subfolder name when creating the file subscription. Each attribute in the macro uses the syntax {[Attribute Name]@[Attribute Form]}.
For example, if your report has Manager in the page-by axis, you may burst the report into subfolders using the Manager’s last name. In this case, you provide macro text {[Manager]@[Last Name]}as the bursting subfolder name.
You can create multiple levels of subfolders if your report or document is grouped by multiple attributes. As a second example, you could have Manager folders with Category subfolders in each. This macro text may be entered in the subfolder name as {[Manager]@[Last Name]}-{[Manager]@[First Name]}\{[Category]@[DESC]}. The result of this bursting example is shown in the image below. One of the subscribed reports with books data is in the Books subfolder in the manager’s subfolder named Abram-Crisby.
In the example above, the Reports\FileDev1 path was defined as part of the file device used for the subscription. The file name has the date and time appended to the report name because the file device definition has the Append timestamp to file name check box selected.

To burst a file subscription across multiple subfolders

1Create a file subscription in MicroStrategy Web.
2In the Subscription Editor, click Burst… The Select Bursting Criteria options are displayed. All attributes used to group data in the report or document are shown in the Available Attributes list.
3From the Available Attributes list, select any attribute to use to create the subfolders, then click the right arrow to move the attribute to the Selected Attributes list. The Sub-folder field displays below or to the right of the File Name field.
4To change the order of attributes for bursting, select an attribute in the Selected Attributes list, then click the up or down arrow.
5In the File Name field, type a name for the files to be created. You can use macros to ensure that each file has a unique name.
6In the Sub-folder field (the one below or to the right of the File Name field), type a macro to dynamically create the subfolders.
7Click OK to save the subscription.

Comments

  1. This is very helpful information for my business regarding subscription management software. Thanks for providing it.

    ReplyDelete

Post a Comment

Popular posts from this blog

Microstrategy Custom number formatting symbols

Custom number formatting symbols If none of the built-in number formats meet your needs, you can create your own custom format in the Number tab of the Format Cells dialog box. Select  Custom  as the Category and create the format using the number format symbols listed in the table below. Each custom format can have up to four optional sections, one each for: Positive numbers Negative numbers Zeros Text Each section is optional. Separate the sections by semicolons, as shown in the example below: #,###;(#,###);0;"Error: Entry must be numeric" For more examples, see  Custom number formatting examples . To jump to a section of the formatting symbol table, click one of the following: Numeric symbols Character/text symbols Date and time symbols Text color symbols Currency symbols Conditional symbols Numeric symbols For details on how numeric symbols apply to the Big Decimal data type, refer to the  Project Design Guide . ...

MicroStrategy URL API Parameters

MicroStrategy URL Structure The following table summarizes the root URL structure used for every request to MicroStrategy Web. Environment Main Application URL Administration URL J2EE http://webserver/MicroStrategy/servlet/mstrWeb http://webserver/MicroStrategy/servlet/mstrWebAdmin .NET http://webserver/MicroStrategy/asp/Main.aspx http://webserver/MicroStrategy/asp/Admin.aspx Every request sent to MicroStrategy Web calls a central controller. Parameters are appended to  Main.aspx  or  mstrWeb  (in a .NET and J2EE environment, respectively) to indicate to the controller how the request should be internally forwarded and handled. The following examples show a URL for accessing a MicroStrategy folder when the user does not have an existing session. The URL contains not only the parameters needed to connect to MicroStrategy Web, but also the parameters needed to log on and create a session. J2EE environment: <a href="http:...

Control the display of null and zero metric values

Show   Control the display of null and zero metric values in a grid report You can determine how to display or hide rows and columns in a grid report that consist only of null or zero metric values. You can have MicroStrategy hide the rows and columns in the following ways: Hide rows and columns that consist only of null metric values Hide rows and columns that consist only of zero metric values Hide rows and columns that consist only of null or zero metric values (default) Once you have defined how MicroStrategy hides null and zero metric values in the grid, you can quickly show or hide the grid using the Hide Nulls/Zeros option in the Data menu, as described below, or by clicking the  Hide Nulls/Zeros  icon  in the Data toolbar. To determine how null and zero metric values are displayed or hidden in a grid report Open the report in Edit mode. From the  Tools  menu, select  Report Options . The Report Options...

Custom Subtotal Displays in MicroStrategy

Defining custom subtotal displays in MicroStrategy By default, when users apply subtotals in a report, the name of the subtotal is displayed in the subtotal line items that appear in the report. Users can use custom subtotals to give more control over the characteristics of a subtotal. Custom subtotals allow users to define custom subtotal line items that appear on the reports  U sers can make the subtotal name dynamic by typing special characters in the subtotal name field as listed in the following table. Character Description #A The name of the attribute under which the subtotal appears. #P The name of the attribute to the left of, or above the attribute under which the subtotal appears. #0 All the forms of the parent element. #1 The first form of the parent element reading from left to right or from top to bottom. #2 The second form of the parent element reading from left to right or from top to bottom. #3 The third form of th...

Case functions Microstrategy

Ca se functions Microstrategy Case functions return specified data in a SQL query based on the evaluation of user-defined conditions. In general, a user specifies a list of conditions and corresponding return values. Case This function evaluates multiple expressions until a condition is determined to be true, then returns a corresponding value. If all conditions are false, a default value is returned.  Case  can be used for categorizing data based on multiple conditions. This is a single-value function. Syntax Case ( Condition1 ,  ReturnValue1 ,  Condition2 , ReturnValue2 ,...,  DefaultValue ) Example Case(([Total Revenue] < 300000), 0, ([Total Revenue] < 600000), 1, 2) sum(Case (Day@DESC in (“Sat”,”Sun”), Sales, 0) {~+} Sum(Case(Category@DESC In("Books","Electronics"),Revenue,0)){~+} CaseV (case vector) CaseV  evaluates a single metric and returns different values according to the results. It can be used to perfo...

Microstrategy Report Services documents and dashboards

Microstrategy Report Services documents vs Dashboards A MicroStrategy Report Services document displays data coming from multiple reports, with the data laid out and designed in presentation-quality format. Most data on a document is from one or more underlying datasets. A dataset is a standard MicroStrategy report. Other document components that do not originate from the dataset, such as static text used for a title or heading, page numbers, and images, are added by the document's designer and are stored in the document's definition. A Report Services (RS) dashboard is a special type of document. An RS dashboard is commonly only one page long, is intended to be viewed online, and usually provides interactive features that let analysts change how they view the dashboard’s data, as well as what data they are viewing. A broad selection of widgets and a wide variety of formatting options allow you to design a customized, interactive dashboard. Both documents and RS dashb...

System Manager workflow to execute on a schedule

Creating a System Manager workflow to execute on a schedule System Manager workflow can execute on a schedule or after an event has been triggered. This can be accomplished by creating a simple batch file, and scheduling that batch file to execute with a third-party tool like Microsoft Task Scheduler.   Note : To avoid user permission conflicts, the following steps must be performed with highest privileges.   In the below example, the workflow makes the i-server restarts every day.   1. The user must first have a valid workflow. This particular workflow is a template that is delivered out-of-the-box with System Manager.   2. Save the workflow in  .smw  format.   3. In a text editor (such as Notepad), enter the command line statement that the task scheduler should execute.     MASysMgr.exe -w C:\filename.smw” “UserName=User1 “Password=1234”   4. Save the file in  .bat  ...

Retrieve a list of user groups and the associated users in MicroStrategy

    Retrieve a list of user groups and the associated users in MicroStrategy Developer 9.x Although MicroStrategy Command Manager 9.x can be used to generate lists of all user groups and all users within a particular group, there is currently no way for it to retrieve a list of all groups and all of the users in each group. If such a list is desired, it can be created using the Project Documentation Wizard in MicroStrategy Desktop Developer 9.x. Follow the steps below to create a list of all groups and the users in each group: In MicroStrategy Developer 9.x, select 'Project Documentation' from the Tools menu to start the wizard. Select any project that is in the project source that contains the users and groups and click Next. Select only Configuration Objects for documentation. Uncheck the 'Basic Properties' object category from the next screen, as shown below: Then select only 'User Group' under the Configuratio...

Report filters are being ignored in Microstrategy report SQL

Report filters are being ignored in Microstrategy report SQL When users run a report using a simple filter, the filter is not applied to the report in MicroStrategy Developer 9.x and 10.x. The results returned to the users are not filtered as expected. The Report SQL indicates that the filter has not been applied. CAUSE: One scenario is that the MicroStrategy 10.x SQL Engine is ignoring the conditionality at the report level because a metric in the report also contains a related conditionality which has been set to "remove related report filter elements" or "ignore" the filtering criteria at the report level. ACTION: When a report contains the above situation, the follow steps can be done to have both filters applied and be merged for the report results to be executed with: If the report's and metric's filter affect attributes from the same hierarchy, check that the following setting is un-checked: This setting is placed in the me...

Settings for Outer Join between metrics in MicroStrategy

Settings for Outer Join between metrics in MicroStrategy MicroStrategy adopts multi-pass logic to determine the execution plan for a report. This means that every metric is evaluated in separate SQL passes. Outer Joins come into play when MicroStrategy Engine merges the results from all SQL passes into one report. For a multi-pass report, different Outer Join behaviors can give the user completely different results. In addition, report metrics can be of different types which can, in some cases, influence the result of the outer join. In MicroStrategy, there are two settings that users can access to control Outer Join behavior : Formula Join Type and Metric Join Type . Metric Join Type: VLDB Setting at Database Instance Level Report and Template Levels Report Editor > Data > Report Data Options Metric Level   Metric editor > Tools > Metric Join Type Control Join between Metrics Formula Join Type: Only at Compound/Split...