Some time in the last 12 months the unique name properly of dimension members
shown through XML/A has changed. For parent-child dimensions the format was
equal to the name property, now it is in the full path top down dot seperated
format.

Can anyone shed any light on what might have caused this change.

Could be

1. Change of the dimension properties
2. Change of MDX Compatibility Mode and/or MDX Unique Name Style connection
string properties
3. Change of MDX Compatibility Mode and/or MDX Unique Name Style server
registry entries.

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebLog/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================

Thanks for this info but it still leaves me with a few questions:

1. Parent-child dimensions always have unique keys and this seemed to be the
driver in the past to the uniquename being in the format of
[Dim].&[keyvalue], this has not changed so I think this discounts this idea.

2. Where would I find the MDX compatibility mode, the connection string has
also not changed because the application remains the same version.

3. Can you give me the path of the registry entries please.

"Mosha Pasumansky [MS]" wrote:

http://msdn.microsoft.com/library/de...egsettings.asp

The names of entries are MDXCompatibilityValue and MDXUniqueNames

--
==================================================
Mosha Pasumansky - http://www.mosha.com/msolap
Analysis Services blog at http://www.sqljunkies.com/WebLog/mosha
Development Lead in the Analysis Server team
All you need is love (John Lennon)
Disclaimer : This posting is provided "AS IS" with no warranties, and
confers no rights.
==================================================