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 UpdateInsert, or Delete data.
Click OK to save your changes.


Comments

  1. We are also noticing that traditional medical doctors are also recognizing the increased interest in holistic healing and are finally starting to incorporate these healing methods into their practice to keep up with the current trends. There are many ways to obtain a construction job interview, but some are more effective than others. strategyleap

    ReplyDelete

Post a Comment

Popular posts from this blog

Slowly Changing Dimension Types 0, 4, 5, 6 and 7

Slowly Changing Dimension Types 0, 4, 5, 6 and 7 Ralph introduced the concept of slowly changing dimension (SCD) attributes in 1996. Dimensional modelers, in conjunction with the business’s data governance representatives, must specify the data warehouse’s response to operational attribute value changes.  Core SCD approaches:  Type 1 (overwrite),  Type 2 (add a row), and  Type 3 (add a column).  Since legibility is a key component of the Kimball mantra, we sometimes wish Ralph had given these techniques more descriptive names, such as “overwrite” instead of “type 1.” But at this point, the SCD type numbers are part of our industry’s vernacular. We have written about more advanced SCD patterns, such as the 2005 article entitled “ Slowly Changing Dimensions are Not Always as Easy as 1, 2, 3. ” However, we’ve not consistently named the more advanced and hybrid techniques. With the third edition of  The Data Warehouse Toolkit  (Wiley, 201...

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:...

Internationalization Design Technics

Microstrategy Internationalization Design Technics MicroStrategy supports data internationalization through two different techniques. You can either provide translated data through the use of extra tables and columns, or you can provide separate databases to store your translated data. These techniques are described below: You can support data internationalization in your database by using separate tables and columns to store your translated data. You can use various combinations of tables and columns to support and identify the translated data in your database. To support displaying the name of each month in multiple languages, you can include the translated names in a separate column, one for each required language, within the same table. Each column can use a suffix to identify that the column contains translated data for a certain language. The same LU_MONTH_OF_YEAR table with translated data for the Spanish and German langua...

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...

Uniquely identifying data using Compound Key in Microstrategy

Uniquely identifying data in tables with Compound Key attribute: The types of keys that can be assigned to a table include: • Simple key requires only one column to identify a record uniquely within a table. • Compound key requires multiple columns to identify a unique record. . The following diagram shows how the different key structures can be used to identify a cal...

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...

Configure Connection Mapping in Microstrategy

Configure Connection Mapping in Microstrategy The following steps demonstrate the second scenario where two different data warehouses are used within the same project: Create two different database connections -                                                                                        One that points to the data warehouse for the European users                                                                 and the other that points to the data warehouse for USA users as shown below: Select Europe as the default database connection for the database Instance as seen below: Go to P...
Star schemas and aggregate (or summary) fact tables Aggregate tables can further improve query performance by reducing the number of rows over which higher-level metrics must be aggregated.  However, the use of aggregate tables with dimension tables is not a valid physical modeling strategy. Whenever aggregation is performed over fact data, it is a general requirement that tables joined to the fact table must be at the same attribute level or at a higher level. If the auxiliary table is at a lower level, fact rows will be replicated prior to aggregation and this will result in inflated metric values (also known as "multiple counting"). With the above Time dimension table, a fact table at the level of Day functions correctly because there is exactly one row in DIM_TIME for each day. To aggregate the facts to the level of Quarter, it is valid to join the fact table to the dimension table and group by the quarter ID from the dimension table. Sql select DT...

OLAP features in Microstrategy

OLAP features in Microstrategy MSTR  OLAP Services uses Intelligent Cube Technology—an in-memory version of report data that can 1 About MicroStrategy OLAP Services  can be manipulated by the MicroStrategy Analytical Engine. MicroStrategy Desktop, Web, and Office users can slice and dice data in reports within Intelligent Cubes without having to re-execute SQL against the data warehouse.  Many of the standard OLAP features that MicroStrategy provides out of the box, such as: Page-by Pivoting Sorting Subtotals Banding Aliasing Outline mode Thresholds etc.. With an OLAP Services license, user can perform additional OLAP analysis, using the following features:  Displaying data on the fly: dynamic aggregation, page  Creating metrics on-the-fly: derived metrics, Defining attribute elements on-the-fly: derived elements,  Filtering data on the fly: view filters and metric filters,  Importing data as an Intelligent Cube

Data Mart Reports in Microstrategy

Creating Data Mart Reports in Microstrategy   When there is requirement to store all the report results to a database table you can use the interesting feature in Microstratgey called Data Mart Reports. To create a data mart table, you first create a data mart report that defines the columns of the data mart table. You then create the data mart table and populate it with data. The steps below walk you through the process of creating a data mart report and then executing the report to create a data mart table. The steps also include an example for most steps, based on Tutorial sample data in the MicroStrategy Tutorial project.                Follow the simple steps below to create a datamart report: 1 In MicroStrategy Developer, create a new report or select an existing report to use as the data mart table. The report should contain the attributes...