Right now we're looking at using AMO to programmatically translate the various OLAP elements (we also looked at directly modifying the XML/A deployment script, but aren't pursuing that option for process reasons). There are some concerns about this approach, however. There doesn't seem to be a language-independent way to identify specific OLAP objects from an OLAP client (there is an ID property on some objects, but as far as I can tell it isn't usable from ADOMD.NET, and it isn't present on all objects anyway). In other words, in our admin tools if we want to query a specific cube, there's no language independent way to reference it.
Also, if we change the names of, for example, a measure, we also need to change the expression for any calculations that reference that measure.
Is there some more elegant solution that we're missing here?
Thanks,
Kevin
Kevin.
You can argue back and fourth but looks like the answer for your case is to use translations :).
And that is the feature desinged specifically for the case you describe.
Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Anyway, it sounds like you're saying that isn't much of a good alternative here that supports SE.
No comments:
Post a Comment