KB45573: In MicroStrategy Analytics Enterprise the behavior may be inconsistent when running a document based on an extended data access (XDA) report in a different locale.

It is generally not a problem when running an extended data access (XDA) report alone. The problem will be encountered using the Cube Join feature supported in Strategy Analytics Enterprise; XDA reports do not support Data Internationalization. Take a FreeForm SQL Report as an example. Users can write SQL to select any column in any language, so this has the potential to have different forms for the same attribute ID. Take the following example:
 
Create a normal report and a FreeForm SQL report:

• English Locale:
  

• French Locale:
  

• Freeform SQL report (select a different column for Category):
  

Create a document based on those reports in English locale.
The grid is Category, Cost and the grid source is the normal report. The report's results are shown below:

The form of Category uses the Freeform SQL report's Category except one form which only exists in the normal report.  So the Analytical Engine will store the attributes information as follows:
 

 
This behavior is decided by the following rule. If one dataset has an incomplete attribute form or has a different attribute form from the other dataset:

1. If there is a null value form, it will use the non-null value form instead of null.
2. If two datasets have different attribute form, it will use the form with the biggest dataset.
3. If the two datasets have the same number of rows, it will use the first dataset added into the document.