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

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

Prompt-in-prompt(Nested Prompts) in Microstrategy

Prompt-in-prompt(Nested Prompts) in  Microstrategy Nested prompts allows you to create one prompt based on the other and other bases on another, nested prompts allows us to prompt the highest level(Like year) to middle level(like Quarter, then to the low level(like Month). Here you can see how to  create a 3-level deep nested prompt that will prompt the user to select a year, then a quarter within that year, then a month within that quarter. Prompt-in-prompt is a feature in which the answer to one prompt is used to define another prompt. This feature is only implemented for element list prompts . The following procedure describes how to achieve this: Create the highest level filter. This is a filter which contains a prompt on an attribute element list. Create a filter on the attribute "Year." Click "prompt on attribute element list" and click "Next" through the rest of the screens to accept the default values. Do not set any additio...
3 comments
Read more

Types of prompts in Microstrategy

Types of prompts in Microstrategy The different types of prompts allow you to create a  prompt  for nearly every part of a report. Prompts can be used in many objects including reports, filters, metrics, and custom groups, but all prompts require user interaction when the report is executed. The correct prompt type to create depends on what report objects you want users to be able to base a filter on to filter data, as described in the list below. Filter definition prompts   allow users to determine how the report's data is filtered, based on one of the following objects: Attributes in a hierarchy : Users can select prompt answers from one or more attribute elements from one or more attributes. The attribute elements that they select are used to filter data displayed on the report. This prompt lets you give users the largest number of attribute elements to choose from when they answer the prompt to define their filtering criteria. For example, on a repor...
1 comment
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

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

MicroStrategy VLDB properties with Hive

 Recommended VLDB Properties for use of  MicroStrategy 9 with Hive 0.7x The recommended VLDB optimizations for Hive 0.7x are listed below. These values are set by default when the "Hive 0.7x" database object is used (set at  Configuration Managers > Database Instances > Database Instance > Database connection type ) Selected Default VLDB Properties for Hive 0.7x  VLDB Category  VLDB Property Setting  Value   Tables  Fallback Table Type  Permanent Table  Tables  Maximum SQL Passes Before FallBack   0 (no threshold)  Tables  Maximum Tables in FROM Clause Before FallBack  0 (no threshold)  Tables  Drop Temp Table Method  Drop after final pass   Tables  Table Creation Type  Implicit Table  Query Optimizations   Sub Query Type   Use Temporary Table, falling back to IN (SELECT COL) for cor...
Post a Comment
Read more

Types of filters in Microstrategy

Types of filters in Microstrategy Below are the types of filters: 1. Attribute qualification filter These types of qualifications restrict data related to attributes on the report. a) Attribute form qualification Filters data related to a business attribute’s form(s), such as ID or description. •  For example, the attribute Customer has the forms ID, First Name, Last Name, Address, and Birth Date. An attribute form qualification might filter on the form Last Name, the operator Begins With, and the letter H. The results show a list of customers whose last names start with the letter H. b) Attribute element list qualification Filters data related to a business attribute’s elements, such as New York, Washington, and San Francisco, which are elements of the attribute City. • For example, the attribute Customer has the elements John Smith, Jane Doe, William Hill, and so on. An attribute element list qualification can filter data to display only those customer...
5 comments
Read more

RunningSum calculation only on the metric subtotal in MicroStrategy

RunningSum calculation only on the metric subtotal in MicroStrategy Here are the series of steps to setup report objects in which metrics and subtotals so only the  subtotal field  will contain the  RunningSum  and the  regular metric values  will be  standard sum values . 1) Create Metric 1 which is the sum of the fact that is to be in the columns. 2) Create Metric2 as the RunningSum of Metric1.  NOTE:  The  sortby  parameter for the RunningSum should be set to whichever attribute you want the report sorted by. 3) Create Metric3 as Metric1 + (Metric2 x 0) 4) Create a new subtotal called "Max" which is defined as Max() 5) On the Subtotals/Aggregation tab for Metric 3, set the Total subtotal function to be "Max" and select the check box for "Allow Smart Metric" 6) Create the desired report and place the 3 metrics on the report.  NOTE:  Only Metric3 is required on the gri...
2 comments
Read more

Microstrategy Dossiers explained

Microstrategy  Dossiers With the release of MicroStrategy 10.9, we’ve taken a leap forward in our dashboarding capabilities by simplifying the user experience, adding storytelling, and collaboration.MSTR has  evolved dashboards to the point that they are more than dashboards - they are  interactive, collaborative analytic stories . Ultimately, it was time to go beyond dashboards, both in concept and in name, and so  the've  renamed VI dashboards to  ‘ dossiers ’.  Dossiers can be created by using the new Desktop product or Workstation or simply from the Web interface which replaces Visual Insights. All the existing visual Insights dashboards will be converted to Dossiers   With MicroStrategy 10.9, there was an active focus on making it easier to build dashboards for the widest audience of end users. To achieve this, some key new capabilities were added that make it easier to author, read, interact and collaborate on dashboards ...
7 comments
Read more

HyperIntelligence Training Videos

HyperIntelligence  Training Videos           Design and build hyper cards Optimizing Datasets for HyperIntelligence Using the HyperIntelligence for Office Outlook Add-In Building HyperIntelligence Cards Using HyperIntelligence for Mobile on Android Deploying HyperIntelligence for Outlook Insights On-The-Go: HyperIntelligence for Mobile Building HyperIntelligence Profile Cards Designing Custom HyperIntelligence Cards Using the Calendar with HyperIntelligence for Mobile
4 comments
Read more