Skip to main content

Transaction Services - Configure Transactions

Configure Transactions in MSTR Web


Transaction Services-enabled document displayed on an iPhone, iPad, or Android device can allow users to insert/update/delete data in to the database, using the options in the Configure Transactions Editor.

To do so, you must link a Transaction Services report to a grid or to text fields in a panel stack. If the document is being displayed on an iOS device, you can link the report to the cells of a transaction table.

Data from the input objects defined in the Transaction Services report is displayed in the grid, text fields, or cells for users to edit.

Prerequisites:
      Ã˜  You must have the Web Configure Transaction privilege assigned by MSTR user admin.
Ø  Create the Transaction Services report (usually a grid report) you want to link to the grid, text fields, or transaction table cells. Make sure that the Transaction Services report must contain the input object for each value you want to allow users to change. 
Ø  Make sure that the document has been created  with one of the following:
ü  A Grid/Graph that contains a separate attribute form or metric to link to each input object on the Transaction Services report that you want to make editable to the user. Each attribute form you want to link to an input object must be visible in the Grid/Graph. The Grid/Graph should be displayed in Grid View. 
ü  A panel stack that contains a text field to link to each input object on the Transaction Services report. 
ü  A transaction table for display on iOS devices with MicroStrategy Mobile. .

Open the document which has already been created with the grid in it. Right-click the Grid/Graph, transaction table, or any of the text fields in the panel stack, then select Configure Transaction. Navigate to and select a Transaction Services report, then click OK. The Configure Transactions Editor opens.
The following options are available:
Ø  Transaction Mapping options
Ø  Local Transaction options
Transaction Mapping options
Ø  Transaction Report: The name of the Transaction Services report you selected is displayed in the field. To select a different report, click Browse (...) , then navigate to and select the transaction report.
Ø  Input Properties: You can determine how the control used to display each input object is displayed using the Input Properties. The options are:
ü  Transaction Input: The name of each input object in the Transaction Services report is automatically displayed in the Transaction Input column.
ü  Grid Object: Select the attribute form or metric you want to link to the input object. Each input object must be linked to a separate attribute form or metric. This option is only available for Grid/Graphs.
ü  Field: Select the text field you want to link to the input object. Each input object must be linked to a separate text field. This option is only available for text fields.
ü  Editable: Determine whether the user can modify the value displayed in the control.
ü  Control Style: Determine the type of input object control to display, such as a Text Box or Slider. This option is only available if the Editable check box is selected. Click the Control Properties icon to display the Control Properties, then select the appropriate formatting options for the control. The control style determines which formatting options are available. 

Ø  Automatically recalculate values after data change: Determine whether to automatically recalculate subtotals and derived metrics when a user finishes editing a value in a grid linked to a Transaction Services report. This option is available for grids. 
Ø  Mark rows for selection (tabular grid only): Determine whether to display a check box beside each row of data in a grid, to allow the user to choose which values to use to update their data. This option is available for grids.
Ø  Flag cells/fields with modified data: Determine whether to display a flag marker next to any input object control that contains a value the user has modified.
Ø  Submit unchanged record: When a user chooses to submit his changes to the data, there may be input object controls in which he has made no changes. Determine whether to include data only from input object controls in which the user has made changes. This option is available for grids.
Ø  Allow submission without modification: Determine whether to allow users to submit their data without making changes in the input object controls displayed in the document. This option is available for text fields and transaction table cells.

Local Transaction options
Local Transaction options has been introduced in the version 10.4 onwards. Which enables the users to perform transactions such as insert/update/delete when the device is not connected to the internet/network(particularly in offline mode)
This feature will store all the offline transactions and it will perform those transactions once the device it connected to the network and without any user intervention.

Ø  Target dataset: Click the Browse icon (...) to select a dataset to update when offline transactions are performed. The Select Transaction dialog box opens. Navigate to and select the dataset, then click OK.
Ø  Dataset Object: Double-click dataset objects in the list to add them to the CSI statement used to perform offline transactions.
Ø  Field/Grid Object: Double-click fields or grid objects in the list to add them to the CSI statement used to perform offline transactions.
Ø  CSI statement manipulation: Determine whether to Update, Insert, or Delete data.
Click OK to save your changes.


Labels:

Comments

Post a Comment

Popular posts from this blog

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...
3 comments
Read more

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...
Post a Comment
Read more

Disable data blending in MicroStrategy

Disable data blending in MicroStrategy Starting in MicroStrategy 9.4 data blending was made available for documents and dashboards. This permits grid, graph and widget objects to source data from multiple different datasets at the same time.  This is available under the analytical engine VLDB properties inside of project configuration. The property is named "document grids from multiple datasets" and defaults to enabled but can be set to disabled.  Below are the steps to enable/disable the settings of data blending: 1. Go to project configuration by right clicking on specific project(You need admin rights to do this). 2. In the Project configuration windows as shown below select Configure under Project level VLDB settings section. 3. Now it will open the VLDB settings window, select + on " Analytical Engine Settings " and then click on " Document Grids from multiple datasets " option. You will be presented with two...
Post a Comment
Read more

Microstrategy Report Pre and Post Statements

Microstrategy Report Pre and Post Statements Report Post Statement The Report Post Statement settings insert custom SQL statements after the final SELECT statement but before the DROP statements. The settings are numbered 1-5. Each text string entered in Report Post Statement 1 through Report Post Statement 4 is executed separately as a single statement. To execute more than five statements, insert multiple statements in Report Post Statement 5, separating each statement with a semicolon (;). The SQL Engine breaks them into individual statements at the semicolons and executes each separately. The custom SQL is applied to every intermediate table or view. Report Pre Statement The Report Pre Statement settings insert custom SQL statements at the beginning of the report SQL. The settings are numbered 1-5. Each text string entered in Report Pre Statement 1 through Report Pre Statement 4 is executed separately as a single statement. To execute more than five statem...
Post a Comment
Read more

Multi-Table Data Import(MTDI) from one or more supported data sources

Multi-Table Data Import(MTDI) from one or more supported data sources In MicroStrategy Analytics Enterprise Web 10 onewards, users can now simultaneously import two or more tables from one or more supported data sources, this feature is called Multi-Table Data Import (MTDI) which has been renamed as Super Cubes in MSTR 2019 (Does it sound like multisourcing for all the users without admin help?) Currently, all connectors in MicroStrategy Web 10 except " OLAP " and " Search Engine Indices " support Multi-Table Data Import. Users are able to add multiple tables/files when doing data import from single connector, as shown below: Users are also able to combine multiple tables/files from different sources and store them into one single Intelligent Cube, as shown below:
Post a Comment
Read more

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:...
2 comments
Read more

The logical table size calculation in Microstrategy

The logical table size calculation in Microstrategy The logical table size is an integer number that represents the granularity or level of aggregation of a particular table. It is called 'logical' because it is not related to the physical size of the tables (number of rows). It is calculated according to the attribute IDs that are present in the table and their level in the system hierarchy.   Even though, the number does not reveal the actual number of rows in the table, it is an accurate way of measuring a table size without having to access its contents.   MicroStrategy Engine utilizes an algorithm based on attribute keys to calculate the Logical Table Size (LTS):   Given the following tables:     The algorithm that calculates the table sizes performs the following steps: Calculate the number of levels per hierarchy: Hierarchy 1: 3 Hierarchy 2: 4 Calculate each attribute individual weight according to the level in the hierarchy (level in hierarchy/number of ...
Post a Comment
Read more

Apply or Pass-through functions in Microstrategy

Ap ply (Pass-Through) functions MSTR Apply functions provide access to functions or syntactic constructs that are not standard in MicroStrategy but are provided by various RDBMS systems.. Syntax common to Apply functions Apply Function Name   ("expression with placeholders", Arg1, Arg2, Arg3, …ArgN) where: Apply Function Name  – is a generic name used for the predefined pass-through functions described above expression with placeholders  – is the string describing the actual expression or syntax that the engine uses while generating the SQL and which is sent to the RDBMS. The placeholders are represented by #0, #1, and so on. "#" is a reserved character for MicroStrategy. Arg  – is an argument that replaces the parameter markers in the pattern. Arg1 replaces #0, Arg2 replaces #1, and so on. There are   five  pre-defined Apply functions to replace regular, predefined functions of the same type. For more details, cli...
6 comments
Read more

Update the data on an Intelligent Cube without having to republish the entire cube in MicroStrategy

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 only new data. This can reduce the time and system resources necessary to update the Intelligent Cube periodically versus a full republish. For example, if a user has an Intelligent Cube that contains weekly sales data, the user may want this Intelligent Cube to be updated at the end of every week with the sales data for that week. By setting up incremental refresh settings, he can make it so that only data for one week is added to the Intelligent Cube, without affecting the existing data and without having to reload all existing data. Users can select t...
7 comments
Read more

Components of the MicroStrategy Engine

Components of the MicroStrategy Engine The MicroStrategy Engine consists of three engines:  • SQL Engine  • Query Engine  • Analytical Engine  These individual engines work together to fulfill report requests submitted by MicroStrategy that can be resolved by pure SQL alone.  The SQL Engine is responsible for generating optimized SQL and producing result sets that can be resolved by pure SQL alone. The Query Engine is responsible for executing the SQL generated by the SQL Engine.  The Analytical Engine is responsible for performing any calculation that cannot be resolved with SQL alone.
1 comment
Read more