KB310070: When a geo-attribute is added directly to a dashboard using the 'browse all objects' option in MicroStrategy Web 10.x, no data is returned.

SUMMARY:
This Technical Note describers a known issue when using geo-attributes on dashboards. The impact is limited to the 'browse all objects' option on dashboard in Strategy Web 10.x.  Several workarounds for this issue have been provided below for use in current releases.
 
SYMPTOM:
In Strategy 10.x, no data is returned on the grid when a geo-attribute is directly added to a Dashboard via Web using the 'browse all objects' option.
 
STEPS TO REPRODUCE:
Follow these steps to reproduce the issue in the Strategy Tutorial project.

• Create a new attribute in developer and define/set the ‘geographical role’ option (e.g  Zip Code), to make it a geo-attribute.
  

• Figure 1: Create a geo-attribute in developer
• Save and close the attribute, then Update Schema
• Create a new Dashboard in Web, select 'browse all object' -> add two attributes to the rows (with one being the geo-attribute created). Notice no data is returned for the geo-attribute.
  

• Figure 2: Create a dashboard in Web using geo-attribute

CAUSE:
This is a known issue identified in Strategy 10.x
 
ACTION:
This issue has been addressed in 10.7 and 10.4 Hotfix 5 or above versions, please upgrade to take advantage of the fix.
 
WORKAROUND:
Users can use any of these options to work around this issue;
Option 1:

1. Use the geo-attribute within a dataset (report), an intelligent cube or Data Import cube.
2. Use ‘Add External Data’ or ‘Add Existing Dataset’ options to add the dataset or Cube into a dashboard
3. Use the geo-attribute from the dataset or Cube in the dashboard

 
Option 2:
Edit the attribute -> modify the attribute form -> change the geographic role to 'None' (from figure 1 above). This will change the attribute from a geo-attribute to a regular attribute which can be used directly on a dashboard.
 
Option 3:
Use a document instead of a dashboard. The geo-attribute can be placed in grid on the document without issue.
KB310070