If the built-in drillthrough does not return translated columns then I don't think that the ASSP version will either as we are just manipulating the recordset that is returned by the default action. I don't use translations normally so I'd have to do some
research to see if this is possible.

I've added a new function called ExecuteDrillthroughAndTranslateColumns - it works like ExecuteDrillthroughAndFixColumns, but it looks up the translated caption from the MDSCHEMA_LEVELS, MDSCHEMA_MEASURES and MDSCHEMA_DIMENSIONS schema rowsets (so it will always
be a little slower than ExecuteDrillthroughAndFixColumns. I think I've got it handling most things so if you could give it a test and let me know if that works for you that would be great.

excel gets crashed on view underlying data with error
"Data could not be retrieved from the database.
Check the database server or contact your administrator. Make sure the external database is available, and try the operating again."

I am getting this error from default language as well when I use ExecuteDrillthroughAndFixColumns function so I believe this is something with excel not with newly developed function.

Adventure Works has some ROLAP dimensions (which are mainly used for drillthrough details) and you sometimes get that error if SSAS cannot find the SQL database - is that database online and is the connection string in Adventure Works point to the correct
server?

I tested the functionality on my cube and I am afraid that I am not getting translated value.

Process:

1) Defined an action for my calculated measure.
2) Brows the cube in excel with old ASSP and got error that ExecuteDrillthroughAndTranslateColumns.
3) updated the reference to your ASSP and brows the cube. Result is that I am getting Fixed column but not the translated one.

Please note that I only translated the column being used in action expression (for testing).

So I'm not doing any "Fixing" of names, I'm effectively looking up the caption by doing the equivalent of "SELECT * FROM $SYSTEM.MDSCHEMA_LEVELS" - what do you see in SSMS when you run that command? Do you see the translationed attribute
names?

Did you have to change the locale identifier in your odc file to get the translated names in Excel or is that being picked up automatically from the regional settings on your machine?

WITH
MEMBER Measures.CategoryCaption AS Product.Category.CurrentMember.MEMBER_CAPTION
MEMBER Measures.SpanishCategoryCaption AS Product.Category.CurrentMember.Properties("LCID3082")
MEMBER Measures.FrenchCategoryCaption AS Product.Category.CurrentMember.Properties("LCID1036")
SELECT
{ Measures.CategoryCaption, Measures.SpanishCategoryCaption, Measures.FrenchCategoryCaption } ON 0
,[Product].[Category].MEMBERS ON 1
FROM [Adventure Works]

But this return the translations of members of attribute not of attribute itself.

yes, i have to provide locale identifier in my odc file to get translated values. How can I verify that my translation are being save in database correctly?

Ah ok - that's going to be the issue then. Excel seems to create a new connection when you drillthrough and when it does that it looks like it resets the Locale Identifier using the actual local off the client machine.

You'll either need to create a test translation for the locale of your workstation. Or you'll need to change your locale or setup a VM with another locale in order to test this.