Project Configuration Default Settings

Set Freeform SQL and MDX objects default security

Click Modify to open the Properties dialog box: Security tab. The ACL you define here is applied as the default ACL for all objects in the project related to Freeform SQL, Query Builder, and MDX cube sources (SAP BW, Microsoft Analysis Services, Hyperion Essbase, and IBM Cognos TM1). This includes objects such as reports, metrics, attributes, MDX cubes, tables, and other such objects that are created with these MicroStrategy features. You can modify this default ACL for any object in a project individually.

Select a default project drill map or click Clear to remove the default drill map from the field.

All projects must have a default drill map; you cannot remove the existing default drill map from this field until you specify a new default drill map. If you try to remove the only default drill map for a project, a message indicates that other objects depend on it. When you search for dependent objects, none are found, because the dependent object is the project itself.

You can disable drilling for the project by selecting an empty drill map, and then clearing the Drill to immediate children/parents checkbox, described below.

When this is selected, Web users can see only personalized drill paths rather than all drill paths. Personalized drill paths are based on each object's access control list (ACL), specified in the Security category of the Properties dialog box. If you set up ACLs, all drill paths are still displayed in Web until you enable Web personalized drill paths.

Note: Selecting this checkbox disables XML caching, which can adversely impact MicroStrategy Web performance.

The object template used to create a new report for any users who have disabled object templates for reports.

Note: The same default object template is used for both reports and Intelligent Cubes.

Select an option to be displayed from the drop-down list if a prompt is unanswered. The options are:

Default: The prompt is answered by the default prompt answer for the prompt in the target report.

Blank: There is no prompt in the target report.

Prompt Not Answered: The prompt in the target is ignored, which means that the prompt is not answered. No prompt answer is provided from the source and the user is not prompted to provide answers.

No Selection: The prompt is answered using none of the object selected in the source.

All/None: The prompt is answered using all the objects or none of the objects selected in the source.

You can specify whether and how you want to display the attribute name for the attribute element list prompts in the document. The options are:

Yes to show the attribute names.

No to exclude the attribute names.

Repeated to repeat the attribute name for each prompt answer.

Delimiters are characters that can appear around object names to set them off from other text. Braces { } are used as delimiters. You can select the following options from the drop-down list:

Yes to display delimiters for all metadata object names

No to exclude delimiters for all metadata object names

Automatic to display delimiters only for those object names that contain a special character. Special characters are characters other than a - z, A - Z, 0 - 9, #, _, and . (period).

Determines the display of the attribute’s name in the filter’s attribute element list. Select from the following options:

Yes to display the attribute name. This is the default setting.

No to exclude the attribute name.

Repeated to repeat the attribute name for each attribute element. Example: Region = Northeast, Region = Mid-Atlantic.

You can select the text that separates the last two attribute elements in the list. The options are:

custom: The Custom separator field, described below, is enabled when you select this option.

or: The word ”or” is displayed between the last two attribute elements in the list.

and: The word ”and” is displayed between the last two attribute elements in the list.

comma: The comma character , is displayed between the last two attribute elements in the list.

Select this option to display parentheses around each condition, such as (Region = Northeast). The options are:

Yes to display parentheses.

No to exclude parentheses.

Automatic to display parentheses only when it clarifies any ambiguity in the expression.

Use these options to display the details for report objects from the base report or the view report. Select one of the following from the Units from View or Base drop-down list:

To display details for all the objects on the report, that is, all the objects in Report Objects, select Base.

To show details for only those objects displayed on the report grid, select View.

Use these options to select whether the template name of the report is displayed in the Report Details pane. Select one of the following from the Base Template name drop-down list:

Yes: Select this to display the template name for a stand-alone template and the Local Template name for an embedded template.

Automatic: Select this to display the template name for a stand-alone template, but not display the Local Template name for an embedded template. This is the default setting.

No: Select this to omit display of the template name, whether or not the template is stand-alone or embedded.

If you select No watermarks while creating a project watermark, and the Allow documents to overwrite this watermark checkbox in the Project Configuration Editor is selected, a document displays its document watermark, if it is defined for the document. Reports do not display any watermarks when exported to PDF. See Creating document watermarks for more details.

If you select No watermarks while creating a project watermark, and the Allow documents to overwrite this watermark checkbox in the Project Configuration Editor is cleared, all watermarks are disabled. Neither documents nor reports display any watermarks. See Disabling all watermarks for more details.

If you select No watermarks while creating a document watermark, the document does not display any watermark, even if a project watermark has been defined. See Hiding a project watermark for a specific document for more details.

Prompt custom styles

Click Register Styles to associate prompt types with prompt styles, which determine how prompts display in MicroStrategy Web.

This is the maximum number of elements to display in a single request from Developer. Element requests that exceed this limit but are under the project level setting for maximum element rows are stored on the Intelligence Server. This setting impacts how many elements are displayed at one time in Developer's Data Explorer, and in prompt answer windows. Values of 0 and -1 indicate no limit.

Note: If a limit has been specified in the Hierarchy Editor or Attribute Editor that is lower than the limit specified here, that limit is used instead. If the limit specified here is lower than the limit in the Hierarchy Editor or Attribute Editor, this limit is used. If you are not seeing as many elements as you expect, check the attribute’s Limit setting in the Attribute Editor or Hierarchy Editor

If the checkbox is selected, users are allowed to view and delete all dependent objects that may be preventing the object in question from being deleted. A user must have the appropriate ACL access on all dependent objects for the deletion to occur (for details and links to steps, see About controlling access and ACLs).

If the checkbox is cleared, users cannot delete any dependent objects in the project.

If the checkbox is selected, users see the attributes in a hierarchy prompt displayed alphabetically. This setting overrides any specific sorting order defined in the Hierarchy Editor.

If the checkbox is cleared, users see the attributes in a hierarchy prompt displayed according to the sort order defined in the Hierarchy Editor.

Personal answers allow a user to save prompt answers for a specific prompt, and then reuse the answers on any report that uses a prompt.

If the checkbox is selected, prompt designers can allow users to select personal answers while creating a prompt.

If the checkbox is cleared, selecting personal answers for prompts is not allowed.

Select the primary database instance for the project from the Select the Primary Database Instance for the Project drop-down list.

Note: If you have a license for the MultiSource Option, The primary database instance acts as the main source of data for a project and is used as the default database instance for tables added to the project. See the Project Design Help for information on the Warehouse Catalog, and accessing multiple data sources with the MultiSource Option.

SQL Data warehouses

The SQL Data warehouses subcategory is where you create and modify your relational database instances.

You can configure the following settings for relational database instances:

Primary database instance: Select the primary database instance for the project from the Select the Primary Database Instance for the Project drop-down list.

New: Creates a new relational database instance with the Database Instance Editor.

Modify: Lets you modify database instances included for the project (including warehouse, data mart, Freeform SQL, and Query Builder database instances).

Set as default: Sets the selected database instance as the default database instance for the project. The default database instance is the database instance selected by default for Freeform SQL and Query Builder.

VLDB Properties: Modify the warehouse database instance VLDB properties using the VLDB Properties Editor.

Selecting a database instance check box makes that database instance available in the project for standard MicroStrategy reporting, data marts, Query Builder, and Freeform SQL. If you have a license for the MultiSource Option, selecting a check box for a database instance also makes the database instance available from the Warehouse Catalog to be part of the project’s relational schema.

MDX Data warehouse

The MDX Data warehouses subcategory provides settings to create and modify your MDX cube source database instances to connect to MDX cube sources.

You can configure the following settings for MDX cube sources:

New: Creates a new MDX cube source database instance with the Database Instance Editor.

Modify: Lets you modify an MDX cube database instance’s connection information.

VLDB Properties: You can Modify the database instance VLDB properties using the VLDB Properties Editor.

Schema Maintenance: Opens the Schema Maintenance dialog box, which lets you remove MDX database instances from a project, determine when MDX cube schemas are loaded into Intelligence Server, and move MDX cube schemas between different database instances.

The Connection mapping category lists all the connection mappings for the project. It provides the following details:

Database Instance: The database instance that is being mapped to.

User: The user or group associated with the connection mapping.

Language: The default language used by the connection mapping.

Database Connection: The database connection used by the mapped database login.

Database Login: The database login ID that the users are mapped to.

The maximum size for a file to be imported for use as a data source. Files larger that this value cannot be opened during data import. The default value is 100 MB, the minimum value is 1 MB, and the maximum value is as follows:

Files from disk: 4 GB

Other sources: Dependent on Intelligence Server

Defines the maximum size of all data import cubes for each individual user regardless of whether they are published to memory or on disk. You can set the maximum size quota by entering one the following values:

-1: Unlimited - No limit is placed on the size of data import cubes for each user.

0: Default - The default size limit of 100 MB is applied to each user.

1+: Specific limit - Entering a value of 1 or greater will apply a MB limit of that size to each user.

In a clustered environment this setting applies to all nodes in the cluster.

If this option is enabled, you can modify the following:

Enable prompted report caching

Enable non-prompted report caching

Select this checkbox to enable XML caching for reports. XML caching stores the attributes to which all users in Web can drill in the report’s XML cache.

Note: If you select the Enable Web personalized drill paths checkbox from the Project definition Drilling category, XML caching is disabled, which may adversely impact MicroStrategy Web performance.

Determine what cache creation is based on: by user, by database login, and/or by database connection.

Important: If you use database authentication, for security reasons MicroStrategy recommends selecting the Create caches per database login checkbox. Doing this ensures that users who execute their reports using different database login IDs cannot use the same cache.

Define the maximum number of caches allowed in the project at one time.

Note: The default value for the maximum number of caches is 10,000. The maximum value that you can set is 999,999. If you enter any positive value greater than 999,999, the value sets itself to 1,000,000. If you enter ?, Intelligence Server uses the default value.

Define the maximum number of caches allowed in the project at one time.

Note: The default value for the maximum number of caches is 100,000. The maximum value that you can set is 999,999. If you enter any positive value greater than 999,999, the value sets itself to 1,000,000. If you enter ?, Intelligence Server uses the default value.

Purge Object Cache

Click Purge Now to delete all object caches.

Purge element caches

Click Purge Now to delete all element caches.

Defines the amount of data required for all Intelligent Cubes to limit the amount of Intelligent Cube data stored in Intelligence Server memory at one time for a project. The default is 256 megabytes.

The total amount of memory used on Intelligence Server by Intelligent Cubes for a project is calculated and compared to the limit you define. If an attempt to load an Intelligent Cube is made that would exceed this limit, an Intelligent Cube is removed from Intelligence Server memory before the new Intelligent Cube is loaded into memory.

Defines the limit of how many Intelligent Cubes are stored in Intelligence Server memory at one time for a project.

The total number of Intelligent Cubes for a project that are stored in Intelligence Server memory is compared to the limit you define. If an attempt to load an Intelligent Cube is made that would exceed the limit, an Intelligent Cube is removed from Intelligence Server memory before the new Intelligent Cube is loaded into memory.

Select this checkbox to define your Intelligent Cubes to use and support connection mapping. If you do not define Intelligent Cubes to support connection mapping when connection mapping is used in a project, users may be able to access data they are not intended to have access to.

When an Intelligent Cube that supports connection mapping is published, it uses the connection mapping of the user account that published the Intelligent Cube. Only users that have this connection mapping can create and view reports that access this Intelligent Cube. This maintains the data access security and control defined by your connection mappings.

If an Intelligent Cube needs to be available for multiple connection mappings, you must publish a separate version of the Intelligent Cube for each of the required connection mappings.

Select this checkbox to include the process of loading all published Intelligent Cubes as one of the tasks completed when Intelligence Server is started. Report runtime performance for reports accessing Intelligent Cubes is optimized because the Intelligent Cube for the report has already been loaded. However, the overhead experienced during Intelligence Server startup is increased because of the processing of loading Intelligent Cubes.

You can clear this checkbox to exclude the process of loading all published Intelligent Cubes as one of the tasks completed when Intelligence Server is started. The overhead experienced during Intelligence Server startup is decreased as compared to including loading Intelligent Cubes as part of the startup tasks. However, report runtime performance for reports accessing Intelligent Cubes can be negatively affected because the Intelligent Cube must first be loaded into Intelligence Server. To avoid these report performance issues, you can load Intelligent Cubes manually or with subscriptions after Intelligence Server is started.

All reports that access Intelligent Cubes allow you to drill within the data included in an Intelligent Cube. This provides ROLAP-type analysis without having to re-execute against the data warehouse. For example, an Intelligent Cube includes Year and Quarter. A report accessing the Intelligent Cube includes only Year on the report. On the report, you can drill down from Year to Quarter, which returns the results without any extra load on the data warehouse or Intelligence Server.

The decision to enable or disable drilling outside an Intelligent Cube depends on several factors. You should consider the size and complexity of your Intelligent Cubes when deciding whether to enable drilling outside an Intelligent Cube. Enabling drilling outside relatively small Intelligent Cubes can give the benefit of ROLAP analysis through drilling, but enabling this analysis on relatively large Intelligent Cubes can put increased load on your data warehouse and Intelligence Server. See the In-memory Analytics Help for steps to define the drilling behavior of Intelligent Cubes.

Select this checkbox to load Intelligent Cubes into Intelligence Server memory when the Intelligent Cube is published. Intelligent Cubes must be loaded into Intelligence Server memory to allow reports to access and analyze their data.

To conserve Intelligence Server memory, clear this checkbox to define Intelligent Cubes to be stored in secondary storage only when published. The Intelligent Cube can then be loaded into Intelligence Server memory manually, using schedules, or whenever a report attempts to access the Intelligent Cube.

Advanced >>

You can select the categories of staging statistics to be purged for the selected period:

Warehouse catalog

Click Catalog Options to open the Warehouse catalog dialog box. Configure options for the Warehouse Catalog.

If data is available in multiple data sources through MultiSource Option, the primary database instance is used if it has the necessary data. If the data is only available in other secondary data sources, one of the secondary data sources that includes the data is used to retrieve the necessary data using some basic internal logic. Any data source priority you defined using Database Instance Ordering is ignored.

By selecting this option, this MultiSource Option default ordering is used for all reports in a project. You can enable or disable the use of this ordering for individual reports.

Select this checkbox to define a character set and font to override the defaults.

Select the character set to be used for the new graph: Select a character set from the drop-down list. This character set overrides the default character set when creating a new graph.

Select the font to be used for the new graph: Select a font from the drop-down list. This font overrides the default font when creating a new graph.

If you select this option, empty Grid/Graphs display a message as described below.

If no text is entered in the No data returned field, empty Grid/Graphs display the default message (No data returned) in the localized language.

If text has been entered in the No data returned field, empty Grid/Graphs display that text.

(OLAP Services only) Determine how differing report versions will be handled for OLAP Services reports. Previous versions of MicroStrategy clients, such as Web or Developer, may not display correct formatting for OLAP Services reports created or edited and saved in version 9.0 and later. If your environment uses a mixture of 9.0 clients and older clients, select one of the following settings to determine how the system should handle OLAP Services reports.

If a user attempts to save a 9.0 OLAP Services report with the same name as an older report, select one of the settings below to determine the outcome:

Allow without a warning message: The 9.0 report automatically replaces the older report; the user is not warned.

Allow with a warning message: A warning message opens. The user can overwrite the older report, or cancel the save, or change the name of the 9.0 report so that the older report is not overwritten.

Prevent: The user is not allowed to overwrite the older report, and is prompted to save the 9.0 report with a different name.

SQL based