May 23, 2014 at 7:18 am
I have a measure group with sales. One measure [Measures].[sales] is a normal measure read from relational DB. [Measure].[sales last year] is calculated
SCOPE(...);
([Measures].[sales last year])=(ParallelPeriod([Time].[Time].[Year],1,[Time].[Time].CurrentMember),[Measures].[sales]);
END SCOPE;
The measure group works as expected in its own cube. But there is a second cube that links this measure group and there [Measures].[sales] has values but [Measure].[sales last year] is always 0. I queried sales per year.
Is it normal, that a calculated measure (using scope) does not work when linked?
By the way, what is the correct name for this type of measure, is no ordinary calculated measure.
May 28, 2014 at 7:48 am
I don't think the issue is with scope specifically but with having a calculated measure.
When you query a cube that contains a linked measure group, the link is established and resolved during the first calculation pass of the destination cube. Because of this behavior, any calculations that are stored in the linked measure group cannot be resolved before the query is evaluated. In other words, calculated measures and calculated cells must be recreated in the destination cube rather than inherited from the source cube.
June 1, 2014 at 11:52 pm
I had hoped a calculated measere in the processing script (the scope statements) were more reliable. They are certainly not the same as calculated measures "with member...". I know that "last year sales" do work with multi select on time using scope, only. So how do you distinguish them by label?
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply