Skip to main content

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 NameSub-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 Namefield, 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

1Do one of the following:
For a report, click the name of the report to run it.
For a document, edit the document in Design Mode or Editable Mode.
To edit a document in Design Mode, from a folder, right-click the document and select Edit. If the document is open in Presentation Mode, click the menu icon Menu icon (the hamburger) on the right, and select Edit.
To edit a document in Editable Mode, from a folder, right-click the document, point to Run as, and select Editable.
2From the Home menu, point to Subscribe to, and select FTP. The Subscribe to FTP dialog box opens.
3From the Schedule drop-down list, select a schedule or event on which to deliver the report or document. You can create new schedules in the MicroStrategy Developer Schedule Manager. 
4Determine the delivery location (recipient) for the report or document by doing one of the following:
If the FTP server that you want to deliver the report or document to is available in the drop-down list next to Location, select the FTP server.
To add delivery locations to the drop-down list, click Location. The Recipients Browser dialog box opens. Perform the following steps:
aTo add existing delivery locations, use the Add to Selections arrow Add to Selections icon to move one or more locations from the Available list on the left to the To list on the right.
bTo add delivery locations to the drop-down list, type a name for the new delivery location in the Address Name field. In the Physical Address field, specify the folder path to a new or existing folder on the FTP server where the files will be delivered. For example, a properly specified path is: FTPdelivery/reportfolder. From the Devicedrop-down list, select your FTP device. When you are finished defining the new delivery location, click Add to Recipients.
*Any locations you create must be accessible from the machine on which Distribution Services is installed.
cClick OK when you are finished adding delivery locations.
5From the Delivery Format drop-down list, select the format in which to send the report or document.
6You can reduce the size of the report or document by including it in a zip file. Select the Compress contents check box.
7If the report or document contains grouped objects, do one of the following:
To print the data for all objects, select the Expand page-by fields check box.
To print the data only for the objects currently selected in the Page-by panel (for reports) or the Grouping panel (for documents), clear the Expand page-by fields check box.
8Type a name for the file in the File Name field.
9To replace all spaces in the file name with another character, in the Delimiter field, type the character to replace all spaces with. To see a list of characters that cannot be used as space delimiters, hover the cursor over the information icon Example of an information icon.
*Spaces that are created by expanding macros, such as a space between the time and date in a timestamp, are not replaced by the space delimiter.
10If prompt answers are displayed, select the prompt answers to use whenever the report or document is delivered.
11Expand the Advanced Options.
12For reports or documents included in a zip file, you can password protect the zip file for additional security. Select the Password protect zip file check box and type a password for the zip file. This option is available only when the Compress Contents check box is selected.
13If you chose to include the report or document in a zip file, you can specify a name for the zip file. Type the name in the Zip File Name field. This option is available only when the Compress Contents check box is selected.
14To specify a date after which to stop delivering the report or document, select the Do not deliver after check box, then select the date from the calendar.
15By default, if you have selected a contact group as the recipient of the report or document, MicroStrategy uses the security filter of the contact group as a whole when delivering the report or document. To use the separate security filters for each member of the subscribed contact group instead, select the Use contact security for each group member check box.
16To have a notification email sent when the report or document is delivered, select the Send notification to email address check box, then do one of the following:
To send the notification to an email address that has already been defined, select an address from the To drop-down list.
To send the notification to a new email address, in the New Addressfield, type the email address you want to send a delivery notification to and select the email client type of the specified email address from the drop-down list.
17Click OK. The file will be delivered to the specified location on the specified schedule.
To verify that you are subscribed to the report or document, click the MicroStrategy icon Projects icon at the top of the page and select My Subscriptions. The report appears in the FTP Subscriptions list.

Comments

Popular posts from this blog

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 dialog box opens. To determine how

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

Metric values are repeated across rows when a report is executed in MicroStrategy

Metric values are repeated across rows when a report is executed in MicroStrategy When comparing report results between DB Query Tool and MicroStrategy, some reports show repeated metric values in MicroStrategy where there were none in DB Query Tool. To illustrate the issue, a fact table CAT_ITEM_SLS has been added into the MicroStrategy Tutorial project and populated with a small set of three rows. CAT_ID ITEM_ID REVENUE  1 1  10   1 2  20  2  2  30  Report results in DB Query Tool: Report results in MicroStrategy: In MicroStrategy, the row for "Art As Experience" in the Spring 2007 catalog repeats the $20 value from the Winter 2007 catalog, where DB Query Tool shows the $30 value from the fact table. CAUSE The discrepancy occurs because the attribute elements for Catalog and Item are in a many-to-many relationship, but the attribute relationship in the MicroStrategy schema is defined incorrectly with a one-to-many relationship. Not

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 without any formal training. In fact, the add

Enabling the Quick Search feature for MicroStrategy Web

Enable the quick search for MicroStrategy Web When exporting a report containing an image attribute form (using an ApplySimple statement) to PDF in MicroStrategy Web 9.4.1 and 10.x, with the Intelligence Server running on Linux, the image in the exported PDF report appears as a red "X" as shown below: However, the images in the report display properly when the report is executed in MicroStrategy Developer and Web. Furthermore, when the report is exported to PDF on Desktop (with the original images saved in WebASPX\Images), the images in the report display properly, as indicated below: CAUSE This is expected behavior. When the report is displayed in MicroStrategy Developer and Web, or when the report is exported to PDF from MicroStrategy Developer, images in the "WebASPX\Images" folder are used. However, when a report that contains images is exported to PDF from Web, the Intelligence Server will attempt to reference the location in the

Microstrategy Caches explained

Microstrategy Caches Improving Response Time: Caching A  cache is a result set that is stored on a system to improve response time in future requests.  With caching, users can retrieve results from Intelligence Server rather than re-executing queries against a database. To delete all object caches for a project 1 In Developer, log into a project. You must log in with a user account that has administrative privileges. 2 From the  Administration  menu, point to  Projects , and then select  Project Configuration . The Project Configuration Editor opens. 3 Expand  Caching , expand  Auxiliary Caches , then select  Objects . To delete all configuration object caches for a server 1 Log in to the project source. 2 From the  Administration  menu in Developer, point to  Server , and then select  Purge Server Object Caches . 4 Click  Purge Now . To purge web cache follow the steps in the link below: https://microstrategyanalytics.blogspot.com/2018/12/purge-we

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 customers sp

Microstrategy Document Editor Sections Important Notes:

Microstrategy Document Editor Sections Important Notes: The Layout area is in the center of the Document Editor interface and provides the framework for precisely controlling where controls (such as text fields, grid and graph reports, images, and widgets) are displayed when the document is viewed in different display modes, printed, exported, emailed, and so on. To add data to the document, drag objects from the  Dataset Objects  panel and drop them into the  Layout  area. Controls are rendered differently depending on what section they are placed in, as described below:   Page Header : The control is displayed at the top of each page in the document. By default, if a document contains multiple layouts, the same Page Header is displayed for all layouts in the document. You can change this setting so that each layout has a separate Page Header. Document Header : The control is displayed once at the beginning of the document, immediately below the Page Header section. Any data fields pl
Microstrategy Release Types Platform release Interval:  Annually every twelve (12) months in December Who:  Entire customer base What:  Focus on production level security, stability, and performance defect fixes for all customers. Expectation:  Customer has chosen platform path and wants product stability without new enhancements. Support:  Three (3) years, patches for approved P1 defects, and regular hotfix cadence addresses critical defects. Feature Release Interval:  Quarterly every three (3) months Who:  Customers with specific feature requirements. What:  New functionality developed in close collaboration with customers and customer council. Expectation:  Customer has chosen feature path, will consume further feature releases. Support:  Six (6) months patch support for approved P1 defects and (eighteen) 18 months troubleshooting. Customers upgrade to next feature release for roll-up fixes. Why has MicroStrategy introduced “Platform” and “Feature

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