Disabling dynamic sourcing for attributes

Attributes are available for dynamic sourcing by default, but there are some data modeling conventions that should be considered when using dynamic sourcing. In general, if attributes use outer joins, accurate data can be returned to reports from Intelligent Cubes through dynamic sourcing. However, if attributes use inner joins, which is more common, you should verify that the attribute data can be correctly represented through dynamic sourcing.

Two scenarios can cause attributes that use inner joins to return incorrect data when dynamic sourcing is used:

• Attribute information in lookup and fact tables includes NULL values.

• All attribute elements in fact tables are not also present in lookup tables.

These scenarios are uncommon. However, if some attributes fit these scenarios, you can disable dynamic sourcing when these attributes are used in reports and Intelligent Cubes. You can enable and disable dynamic sourcing for attributes by modifying the Attribute Validation VLDB property. This VLDB property has the following options:

• Attribute columns in fact tables and lookup tables do not contain NULLs and all attribute elements in fact tables are present in lookup tables: This is the default option for attributes, which enables attributes for dynamic sourcing.

• Attribute columns in fact tables and lookup tables may contain NULLs and/or all attribute elements in fact tables are not present in lookup tables: This option disables dynamic sourcing for attributes. This setting should be used if your attribute data is not modeled to support dynamic sourcing. The inclusion of NULLs in your attribute data, or a mismatch between available attribute data in your fact and lookup tables, can cause incorrect data to be returned to reports from Intelligent Cubes through dynamic sourcing.

You can disable dynamic sourcing for attributes individually or you can disable dynamic sourcing for all attributes within a project. For information on defining default dynamic sourcing behavior for attributes, see Accessing the dynamic sourcing VLDB properties for a project.

The steps below show you how to disable or enable dynamic sourcing for an individual attribute.

Prerequisite

• An attribute has been created in a project.

To enable or disable dynamic sourcing for an attribute

1. In MicroStrategy Developer, browse to an attribute, and then right-click the attribute and select Edit. The attribute opens in the Attribute Editor.

2. From the Tools menu, select VLDB Properties. The VLDB Properties Editor opens.

3. From the Tools menu, select the Show Advanced Settings option if it is not already selected.

4. In the VLDB Settings list, expand Dynamic Sourcing, and then select Attribute Validation.

5. Clear the Usedefault inherited value check box.

6. Select one of the options depending on whether you want to disable or enable dynamic sourcing for an attribute:

   • To enable attributes to use dynamic sourcing (the default option), select Attribute columns in fact tables and lookup tables do not contain NULLs and all attribute elements in fact tables are present in lookup tables.

   • To disable dynamic sourcing for attributes unless outer joins are used for the attribute, select Attribute columns in fact tables and lookup tables may contain NULLs and/or all attribute elements in fact tables are not present in lookup tables. This setting should be used if your attribute data is not modeled to support dynamic sourcing.

7. Click Save and Close to save your changes to VLDB properties and close the VLDB Properties Editor.

8. Click Save and Close to save the attribute and close the Attribute Editor.