Developer Preferences: Optional Actions category, General preferences

From the Optional Actions category on the left, you can specify the following general preferences, which display a warning message or a confirmation message when you perform certain actions in MicroStrategy Developer, as described below. You can select any combination of the following:

• Ask for confirmation when removing a unit from a report: Selecting this option displays a confirmation message any time you move an object off a report. The confirmation message gives you the opportunity to cancel the move if you do not want to move the object off the report.

• Display change journal comments input dialog: If this option is selected and change journaling is enabled, every time you save an objectyou are prompted to enter a comment for the change journal explaining the change.

• Display Template Dependency Validator: If you select this check box, the Template Dependency Validator is displayed whenever a template is modified or saved. The Validator lists any reports that will no longer run after changes to the template are completed. For details on how the Validator works, see Template Dependency Validator.

Tip: Selecting this option also allows you to display the Template Dependency Validator if you previously selected the Do not show this dialog box in the future check box in the Template Dependency Validator but now want to see the message again.

• Warn on connect when server version is newer than client version: If you select this check box, a warning message is displayed when you log in to a project in MicroStrategy Developer through an Intelligence Server that is a later version than the version of MicroStrategy Developer you are logging into.

  • You can, in some cases, connect an older MicroStrategy Developer client to a newer Intelligence Server. (See the MicroStrategy Upgrade Guide for specific details.) However, in these configurations you cannot benefit from the enhancements that a same-version combination offers. For example, if you connect MicroStrategy Developer 7.5.x to Intelligence Server 8.x, while you can use MicroStrategy Developer in this configuration, you cannot benefit from the performance and other features provided by an 8.x MicroStrategy Developer client and server combination. In general, using the same versions of clients and servers within the MicroStrategy platform results in more efficient and reliable system performance.

  • If you plan to upgrade the MicroStrategy Developer client in the near future, it is recommended you select this check box. If you do not plan to upgrade MicroStrategy Developer, you can clear this check box so you are not prompted by the warning message in the future.

• Warn on connect when the metadata requires an update: When a project is accessed for the first time after a new version of MicroStrategy Developer is installed, a warning message to update the metadata is displayed. It is highly recommended you update your metadata when prompted so it is synchronized with your current versions of MicroStrategy Developer and Intelligence Server. If you do not update your project metadata, it can result in loss of functionality and unexpected behavior in MicroStrategy Developer. Also, your project cannot benefit from the enhancements of the newer metadata version.

  • If you choose to update the metadata at another time, a warning message alerts every user accessing the project that the metadata has not been updated. Clear this check box to disable the warning message.

• Warn on document group deletion: A group in a document is a set of data that the document designer grouped to display the data in a readable manner.Selecting this option displays a confirmation message any time you choose to delete a group from a document. The confirmation message gives you the opportunity to cancel the deletion if you do not want to delete the group from the document.

• Warn on document layout deletion: A single document can contain multiple layouts. Each layout operates as a separate document, with its own grouping page setup, and so on, but the layouts are generated together into a single PDF document. Selecting this option displays a confirmation message any time you choose to delete a layout from a document. The confirmation message gives you the opportunity to cancel the deletion if you do not want to delete the layout from the document.

• Warn on editing dataset/cube: If you select this check box, you are prompted with a reminder message when you edit a dataset report or Intelligent Cube from the Document Editor. The message is a reminder that changes that you make to the dataset are not reflected in the document until you close and re-open the document. Changes that you make to an Intelligent Cube are not reflected in the document until you republish the Intelligent Cube, and close and re-open the document.

• Warn on object deletion: If you select this check box, you are prompted with a message to confirm when you attempt to delete an object. (You must have permission to delete the object, to be able to display this confirmation message.) Clear this check box to disable the confirmation message.

  • If this option is cleared and you have permission to delete the object, the object will not be deleted if other objects depend on it. Instead, a dialog box opens asking whether you want to see the dependent objects.

• Warn on report re-execution: If you select this check box, a warning message is displayed when you modify a report definition, for example by adding an attribute or metric to the report. The warning message that appears is: This manipulation will cause the report to be re-executed. Do you want to proceed?

  • Tip: This option allows you to display the warning if you previously saw the warning and selected the Do not show this message next time check box but now want to see the message again.

• Warn when a column with a character data type is set to be the ID form of an attribute: Some of the attribute forms stored in the columns of some data warehouses are numeric or text/character-based. The ID form category of an attribute is the numeric data, and the DESC form category is the text/character data. Using a column with a text or character data type as an ID column of an attribute can result in SQL generation issues. If you select a column with a text or character data type and set it as an ID column when defining an attribute in the Attribute Editor, a warning message appears. You can either click OK to ignore the message and return to the Attribute Editor, or click Cancel to return to the Create New Attribute Form dialog box. Clear this check box to disable the warning message.

• Warn when data type is incompatible with the form type in MDX cube mapping: When an MDX cube is imported into MicroStrategy using the MDX adapter, MicroStrategy Intelligence Server creates new objects (attributes, metrics, and hierarchies) that reflect the levels of the imported cube. Using the Cube Mapping feature in the MDX Cube Catalog, you can map attribute forms for each attribute contained in the imported cube. If you select this check box, a warning message is displayed if the data type is incompatible with the form type in the MDX cube mapping.

Related Topics

• Developer Preferences dialog box