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

Types of result caches in Microstrategy

Types of result caches Microstrategy The following types of  result caches are created by Intelligence Server: • Matching caches • History caches • Matching-History caches • XML caches All document caches are Matching caches; documents do not generate History caches or XML caches. Intelligent Cube reports do not create Matching caches. Matching caches Matching caches  are the  results of reports and documents that are retained for later use by the same requests later on. In general, Matching caches are the type of result caches that are used most often by Intelligence Server. When result caching is enabled, Intelligence Server determines for each request whether it can be served by an already existing Matching cache. If there is no match, it then runs the report or document on the database and creates a new Matching cache that can be reused if the same request is submitted again. This caching process is managed by the system administrator and ...

Microstrategy "Error type: Odbc error. Odbc operation attempted

 "Error type: Odbc error. Odbc operation attempted: SQLExecDirect. [HYT00:0: on SQLHANDLE] [MicroStrategy][ODBC Oracle Wire Protocol driver]Timeout expired" is shown when executing reports from Web When users are trying to execute some reports in MicroStrategy web in particular, they may receive the Error “SQL Generation Complete Index out of range” and “Timeout expired” error as shown below: Possible Causes: One possible cause is that the MicroStrategy Intelligence Server using a cached database connection that was already dropped by the RDBMS. To resolve this: Admin should delete the database connection caches and create a new DSNs in case they are sharing DSNs to connect to different databases. In addition, change the settings for the ‘Connection lifetime’ and the ‘Connection idle time out’.  Follow the steps below to perform the mentioned changes and verify the report after each step and some of the settings require i-server r...

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

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

No 'Alert' option appear when trying to create an alert-based subscription in MicroStrategy Distribution Services

The 'Alert' option does not appear when attempting to create an alert-based subscription in MicroStrategy Distribution Services In MicroStrategy Distribution Service 9.x and 10.x, and 11.x versions it is possible to create an alert-based subscription. When right-clicking the metric header of a report in MicroStrategy Web 9.0.x, the 'Alerts' option does not appear:    Cause : This issue occurs because the user attempting to create the alert does  not have all of the necessary privileges on alerts.   Fix : In order to create an alert-based subscription, the following privileges are required: In order ti get permissions to create alerts the user should be given the following privileges by the admin: New Version of Microstrategy 11.x: Server- Distribution: Older Versions of Microstrategy 9.x, 10.x etc..: Web Reporter > Web user Web Analyst > Web create alert   ...

Activate MicroStrategy Geospatial Services

Activate MicroStrategy Geospatial Services MicroStrategy 10.11 introduces our new mapping capability: MicroStrategy Geospatial Services, powered by Mapbox. This enhanced map visualization is available for dossiers on all interfaces including MicroStrategy Desktop, Workstation, Web and Library (Mobile included). With MicroStrategy Geospatial Services, MicroStrategy now offers advanced geospatial analytics features that allow users to get more out of their location data. This new feature is available in addition to the out-of-the-box ESRI maps. MicroStrategy Geospatial Services allows users to: Plot polygon shapes for most countries, down to the zip code level Perform powerful interaction between layers (progressively hide or show data layers as zoom levels change) Identify and resolve location name conflicts Add thresholds to data points, size markers for metrics, and color by for both attributes and metrics Fine tune clustering behavior when aggregating data on a ma...

Super Cubes in MicroStrategy 2019

Super Cubes in MicroStrategy 2019 Beginning in MicroStrategy 11.0 and 2019, users will notice objects referred to as " Super Cubes ".  Super Cubes are simply a renaming of what was previously referred to as MTDI (Multi Table Data Import) Cubes. Note that only the naming convention has changed, as the functionality remains the same . This name change is visible in MicroStrategy Workstation and MicroStrategy Web. In MicroStrategy Workstation, right click on any cube created via Data Import and select Properties . The object Type is listed as Super Cube: This can also be seen when editing or authoring a dossier. In your Datasets panel, hover over the name of your dataset. The tooltip will show the dataset type listed as a Super Cube.

Scheduling a report or document to be sent to an FTP in MSTR

Scheduling a report or document to be sent to an FTP server You can have a report or document automatically delivered to a location on your FTP server on a specific schedule. To do so, you must subscribe to the report or document, as described in the steps below. You can customize your subscription by typing macros in the  File Name ,  Sub-folder , or  Zip File Name  fields. These macros are automatically replaced with the appropriate text when the report or document is delivered. For example, you create a subscription to a document. If you type  {&Project}  in the  File Name field, the name of the project in which the document is saved is displayed in the name of the document when it is delivered. • This procedure assumes that an administrator has already added your FTP server as a new device in Developer. Steps to do so are included in the  System Administrator Help . To send a report or document to an FTP server on a schedule ...

Algorithm to calculate Logical Table Size in Microstrategy

How are the fact tables determined using the logical table size for SQL generation 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.   IMPORTANT:   The system hierarchy is defined by the parent-child relationships between attributes of the same family (formerly known as a dimension), not by user-defined hierarchies (i.e., drilling hierarchies).   MicroStrategy Engine utilizes an algorithm based on attribute keys to calculate the Logical Table Size (LTS): Given the following tables: ...

Optimizing queries in Microstrategy using VLDB properties

Optimizing queries in  Microstrategy using VLDB properties #vldb #vldbproperties The table b elow summarizes the Query Optimizations VLDB properties. Additional details about each property, including examples where necessary, are provided in the sections following the table. Property Description Possible Values Default Value Additional Final Pass Option Determines whether the Engine calculates...