Skip to main content

Create a transaction services photo uploader

Create a transaction services photo uploader 
1.  Create a new table "photo_upload" in Tutorial warehouse database
(the default location: C:\Program Files\MicroStrategy\Tutorial Reporting\TUTORIAL_DATA_7200.mdb), as shown below:
 

 2. The 'photo_upload' table has to be pre-populated with *exactly* 10 rows of data, the values for the 'ID' column should be 1-10 and the values for the 'uploaded' column should all be 0

3.  In MicroStrategy Desktop, create a freeform report "R1" based on the new table "photo_upload" in Tutorial data created at step 1, as shown below:
 
SELECT Location, Description, ID, uploaded, numbers
FROM PHOTO_UPLOAD

4.  Create another table for transaction insert SQL. Make sure to create an 'autonumber' type ID as primary key for this table, or auto_increment ID for different DBs.
         
         

5. Create a transaction service report "T1" with "output objects" and "input objects" based on the second table in Tutorial data created at step 4, as shown below:
 
Begin Transaction
INSERT INTO Photo_Upload_Result (Location, Description, ID, Uploaded, Numbers)
VALUES([upload Location@ID],[upload Description@ID],[upload@ID],[uploaded],1)
End Transaction

Place cursor inside the parenthesis and right click to bring up the context menu, then click on define new input to create attribute form or metrics.
 
 Make sure the final output looks like this one
 

6.  Create a Report Services document with report "R1" created at step 2 as dataset and associate "Photo uploader" widget with it. 

7.  Right click the grid and select "configure transaction", configure the transaction as shown below:

 

8.  Create the Action Button for this transaction


9. Make sure the Action button is set to 'Submit'


10. Right click on the Grid object and select Properties and Formatting to set Photo Uploader as the widget under Widget setting unchecking full screen for android phone as following


11. Run the document on iPad, as shown below:
 

    12.  Click "Add Photo" and select photos to upload.
    Labels:

    Comments

    Post a Comment

    Popular posts from this blog

    Personalizing file locations, email and file subscriptions using macros in Microstrategy

    Personalizing file locations MSTr allows to dynamically specify the  File Location  and  Backup File Location  in a file device using macros.  For example, if you specify the  File Location  as  C:\Reports\{&RecipientName}\ ,  all subscriptions using that file device are delivered to subfolders of  C:\Reports\ . Subscribed reports or documents for each recipient are delivered to a subfolder with that recipient’s name, such as  C:\Reports\Jane Smith\  or  C:\Reports\Hiro Protagonist\ . The table below lists the macros that can be used in the  File Location  and  Backup File Location  fields in a file device: Description Macro Date on which the subscription is sent {&Date} Time at which the subscription is sent {&Time} Name of the recipient {&RecipientName} User ID (32-character GUID) of the recipient {&RecipientID} Distribution Services add...
    Post a Comment
    Read more

    Microstrategy Custom number formatting symbols

    Custom number formatting symbols If none of the built-in number formats meet your needs, you can create your own custom format in the Number tab of the Format Cells dialog box. Select  Custom  as the Category and create the format using the number format symbols listed in the table below. Each custom format can have up to four optional sections, one each for: Positive numbers Negative numbers Zeros Text Each section is optional. Separate the sections by semicolons, as shown in the example below: #,###;(#,###);0;"Error: Entry must be numeric" For more examples, see  Custom number formatting examples . To jump to a section of the formatting symbol table, click one of the following: Numeric symbols Character/text symbols Date and time symbols Text color symbols Currency symbols Conditional symbols Numeric symbols For details on how numeric symbols apply to the Big Decimal data type, refer to the  Project Design Guide . ...
    3 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

    Bursting file subscriptions Microstartegy

    Bursting file subscriptions: Delivering  parts of reports across multiple files: Large MicroStrategy reports and documents are often broken up into separate pages by attributes. In a similar way, with Distribution Services, you can split up, or burst, a report or document into multiple files. When the subscription is executed, a separate file is created for each element of each attribute selected for bursting. Each file has a portion of data according to the attributes used to group data in the report (page-by axis) or document (group-by axis). Ex:, you may have a report with information for all regions. You could place Region in the page-by axis and burst the file subscription into the separate regions. This creates one report file for each region. As a second ex:, if you choose to burst your report using the Region and Category attributes, a separate file is created for each combination of Region and Category, such as Central and Books as a report, Central and Ele...
    1 comment
    Read more

    Reduce Intelligent Cube Size By Finding Intelligent Cube Objects Which Are Not In Use

    Reduce Intelligent Cube Size By Finding Intelligent Cube Objects Which Are Not In Use If the i-cubes can potentially be reduced in size an audit can be performed on the cube objects to see which cube objects are not being used by any of the view reports, documents, or dossiers.   The below are examples for a few of the common metadata database platforms . NOTE: To perform this audit, queries are run against the MicroStrategy metadata database. Ensure a metadata backup is taken prior to performing the below actions. Steps: 1) Identify the object ID of the Intelligent cube to be audited by checking the objects Property window 2) Identify the object ID of the project this cube exists within by opening the Project Configuration Sample Cube ID =   CFAF1E9B4D53990698C42E87C7AF2EB5 Sample Project ID =  B7CA92F04B9FAE8D941C3E9B7E0CD754   3) Run the below SQL against the metadata database by replacing the Cube ID and Project ID within the respective ...
    Post a Comment
    Read more
    Using stored procedures within Freeform SQL reports in MicroStrategy Database SQL to Stored Procedure in the DB execute procedure in Freeform Editor in MSTR Microsoft SQL Server CREATE PROCEDURE emp_search @DistCtrID INT as     SET NOCOUNT ON;     SELECT emp_id, emp_first_name + ' ' + emp_last_name     FROM lu_employee     WHERE dist_ctr_id = @DistCtrID; exec sp_ProcedureName @Parameter1= Prompt @Parameter2= Prompt .... ..... After adding the exec procedure statement in Freeform SQL Editor, Add the column for the output columns in the DB stored procedure. https://community.microstrategy.com/s/article/KB37783-Instructions-to-use-stored-procedures-within-Freeform
    Post a Comment
    Read more

    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

    Non Aggregate metrics Beginning lookup, Ending lookup, Beginning fact., Ending fact

    Non Aggregate metrics  Beginning lookup,  Ending lookup,  Beginning fact .,  Ending fact A nonaggregatable metric, such as an inventory metric, is one that should not be aggregated across an attribute.   For example, if you have monthly inventory numbers in your data warehouse and want to calculate the yearly inventory, adding the monthly numbers together does not provide a useful business measure. Instead, you may want to use the end-on-hand and beginning-on-hand inventory numbers to see how the total inventory changed during the year.  The following options are available: • To use the first value in the lookup table, select  Beginning lookup . • To use the last value in the lookup table, select  Ending lookup . • To use the first value in the fact table, select  Beginning fact . • To use the last value in the fact table, select  Ending fact .
    Post a Comment
    Read more

    Mapping columns with BLOB format type in Microstrategy

    Mapping columns with BLOB format type in Microstrategy Columns in the data source that use BLOB format types can be mapped to attribute forms and facts in MicroStrategy as the LongVarBin data type. According to Microstrategy the data types such as Picture, BLOB, Text depending on data can be assigned as LongVarBin data type in the attribute definition. LongVarBin Picture, BLOB, Text depending on data This data type is treated as a long string of binary data.  This representation in MicroStrategy has the following effects on including data from a BLOB format type on a MicroStrategy report or document: • Since the BLOB format type is represented as a LongVarBin, the data is displayed in either binary or hexadecimal representation . The data is not converted into any other format such as an image or PDF format. Therefore, columns in a data source that use BLOB format types to represent images, PDFs, or other non-binary or hexadecimal data should not be include...
    Post a Comment
    Read more