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

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

Like / Contains operator in Tableau

Contains (Like) operator in Tableau SInce there is no like operator in Tableau it provides CONTAINS operator.  Little different syntax is there but not too complex. Syntax for contains is:  Below is the example for using CONTAINS operator in a calculated field in Tableau. IF (CONTAINS([campaign_name],"Intent")) OR (CONTAINS([campaign_name_derived],"Intent")) THEN "Yes"   ELSE "No" END  
Post a Comment
Read more

Microstrategy document/dashboard applying selections as filters or slices

Applying selections as filters or slices In a Microstrategy Document the selections a user makes in a selector can either filter or slice the data in the target: Filtering means that the data for the current selection is calculated only when it is requested by the user. The selections are used to filter the underlying dataset before the metric values are aggregated at the level of the Grid/Graph that is displayed in the document. If the source attribute is not included in the Grid/Graph, the metric values from all the selected elements are aggregated and shown at the level specified in the Grid/Graph. All metric condition selectors (which filter metric values or ranks) and selectors that target other selectors filter data by default. You cannot change them to slicing selectors. Slicing means that the data for each available item in the selector is calculated in advance when the document is first displayed. Selections made while ...
2 comments
Read more

Prompt-in-prompt (Nested prompt) feature in a FreeForm SQL Report

Prompt-in-prompt (Nested prompt) feature in a FreeForm SQL Report In some business scenarios, it is required to implement prompt-in-prompt (nested prompt) feature to use the answer of one prompt to qualify on the elements of another prompt in Freefrom SQL reports in MicroStrategy Developer 9.4.x-10.x. The following procedure describes how to achieve prompt-in-prompt in a Freeform SQL report in MicroStrategy Tutorial project: Create a new filter, select Add an Attribute qualification and choose the highest level attribute Country. Make sure to Qualify On: Elements. Click Prompt as the image shown below. Accept all the default values without any changes in the popped up window after clicking on "Prompt" as shown below. Save the filter as "Country Filter". Click "Prompt", choose "Use a filter to reduce the number of elements" option and select Country Filter created in last step, as shown below. Save the filter as "Region Filter...
Post a Comment
Read more

Custom formatting Microstrategy metric format into 1M 2M etc

Custom formatting metric values of 1,100,000 into a 1.1 million 1.1M type format  In addition to the the pre-defined options for metric formatting, MicroStrategy supports custom formatting. The MicroStrategy Tutorial project is used to explain how users can customize numbers from "1,000,000" to a "1.00" format. Consider a report containing row data values greater than a million, as illustrated below: To format these metric values to use a decimal (i.e., 1.1) instead of showing all the numerals, right-click on the metric (' Revenue ' , for this example) and select  Formatting > Revenue Values , as shown below: Select " Custom " as a category in the Number tab and enter ' 0,,.## ' (without quotation marks), as shown below: Confirm that the format applied properly:
2 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

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

Email Subscription in Microstrategy

Create Email Subscription in Microstrategy Creates an email subscription. Do not include any leading or trailing spaces in the ANSWER parameters. This causes a SQL error and prevents the command from executing. Ex: CREATE EMAILSUBSCRIPTION "New Multi Users" FOR OWNER "administrator" SCHEDULE "Books Closed" CONTACTGROUP "TEST"  CONTENT "Electronics Revenue by Region" IN FOLDER "\Public Objects\REPORTS\SUBJECT Areas\Sales and Profitability Analysis" IN PROJECT "MicroStrategy Tutorial" DELIVERYFORMAT HTML  EXPIRATIONDATE NEVER EXPRIED FILENAME "file_name"   SUBJECT  "Test REPORT" MESSAGE "Please Test"; CREATE EMAILSUBSCRIPTION [ subscription_name ] [FOR OWNER login_name ] SCHEDULE schedule_name  (ADDRESS address_name | USER user_name  | CONTACT contact_name [ADDRESS contact_ address_name ] | CONTACTGROUP contact_group_name ) CONTENT ( report_or_document_name IN FOLDER   loc...
1 comment
Read more
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...
1 comment
Read more