BSO member formula conversion to ASO MDX

Hi guys !
I am trying to convert the following BSO member formula to ASO.
My BSO member formula is :
"FPP70" -> "FPP" / "B70" -> "AP";
In ASO member formula I tried : (FPP70, FPP / B70, AP) but I have a syntax error with '/'
Can anyone please help me out with this?
Thanks,
Jonathan

oops sorry, I made a minor mistake. you don't need the {}
It should be
([FPP70],[FPP]) /([ B70], [AP])
If this is a subset of another calculation you would wrap the whole thing in parens
(([FPP70],[FPP]) /([ B70], [AP]))
([FPP70],[FPP] ) is a tuple

Similar Messages

Essbase 11.1.2.1 - Converting BSO Member Formula to ASO MDX Formula

Hi all,
I'm quite new at Essbase and I'm currently using Essbase 11.1.2.1. I have 2 cubes: one is a BSO cube and the other is an ASO cube.
In the BSO cube, I have an account that has member formula:
IF(@ISATTRIBUTE("US"))
("Sales"->"Budget"->"USD")-("Sales"->"Actual"->"USD");
ELSEIF(@ISATTRIBUTE("EU"))
("Sales"->"Budget"->"EUR")-("Sales"->"Actual"->"EUR");
ELSEIF(@ISATTRIBUTE("UK"))
("Sales"->"Budget"->"GBP")-("Sales"->"Actual"->"GBP");
ENDIF
Notes:
- Sales is an account
- US, EU, and UK are members of Country attribute dimension
- Budget and Actual are members of Scenario dimension
- USD, EUR, and GBP are members of Currency dimension
I understand that the member formula for BSO and ASO are different. Can anyone please advise me on what the formula should be in ASO cube as MDX formula?
Thank you very much!

CASE [Currency].CurrentMember.[Country]
     WHEN "US" THEN ([Sales], [Budget], [USD]) - ([Sales], [Actual], [USD])
     WHEN "EU" THEN ([Sales], [Budget], [EUR]) - ([Sales], [Actual], [EUR])
     WHEN "UK" THEN ([Sales], [Budget], [GBP]) - ([Sales], [Actual], [GBP])
     ELSE 0
END
*Note that I am assuming Country is an attribute of Currency based on the information provided.

Essbase 9.3 BSO member formula problem

Hi All,
I'm working on Essbase 9.3.1.
We have an issue where a member formula, should use double quotations (") for a few members.
In the dimension tables these quotes are not present in the formula, but they come up in the outline of the cube.
All dimension builds are done through AIS because of which I'm in a fix.
I've only worked on Essbase 7 and I'm not aware if there are any settings that I could look at in AIS to see if these quotes are appended while the dimensions are being built.
The reason why this is an iss is that the test outline has the quotes, but the production outline does not have them although its the same flat file that is used for both.
Please help out here.
Thanks in Advance.
Regards,
Anindyo

Obviously this won't resolve your entire problem, but just to answer the first question you can definitely use e.g. @GENMBRS successfully in the partition definitions for a single BSO cube over multiple ASO cubes in 9.3.1.

BSO to ASO Formula Conversion - Help Needed

ASO is not my forte...I am trying to get a simple formula to work in ASO cube as part of BSO->ASO conversion.
If it is level 0 entity, the formula is (Last Shipped (PU) * Part Volume)...works fine.
If its upper level, it should just sum the values of its children. The BSO equivalent that we typically use is @SUM(@CHILDREN(@CURRMBR("Entity"))).
I attempted the same in the ASO MDX script as shown below, it is not yielding me the correct result....any thoughts why this is not working?
Thanks in advance.
Nima
Member Formula*
CASE WHEN ISLEVEL(Entity.CurrentMember, 0) THEN+
Last Shipped (PU) x Part Volume+
ELSE+
SUM(Children(Entity.CurrentMember))+
END+
Edited by: Nima.V on Nov 12, 2008 7:12 PM

Have you tried specifying which measure you want it to sum?
e.g.
CASE WHEN ISLEVEL(Entity.CurrentMember, 0) THEN
Last Shipped (PU) x Part Volume
ELSE
SUM(Children(Entity.CurrentMember), [Measure].[Part Volume])
END
also I'm not sure whether the SUM is correct. This might work as it definately specifies the tuples:
SUM({Products.CurrentMember.children},[Measures].[Part Volume])
hope it helps,
Gee

Problem working on member formulas in ASO cube

Hi
I was asked to convert a planning application BSO cubes into a single ASO cube.I have managed to convert one BSO Cube into ASO through EAS console and added the members in the other BSO cube throgh rulesfile.
Now i have to write the member formulas for the level0 members of Account dimension.These are very simple formulas like
if(@ISMBR("New_Seats"))
"Assets Value"="Total Asset Cost";
else
"Assets Value"="Asset_Value";
endif;
and
"Empty_Seats"=(("New Seat Additions"+"Available_Seats")-"Required_Seats");
This is the first time i am working on ASO.I am getting this error while writing these formulas
"Error(1260052) syntax error in input mdx query on line 1 at token '=' Empty_Seats..."
Help me in writing these formulas and also in selecting proper member properties.

The hierarchy is like
Account(gen1)
-> Statistical_Account(gen2)
->New Seat Additions(gen3)
I have tried tthis and the formula is verified successfully
*([Statistical_Account].[New Seat Additions]+[Statistical_Account].[Available_Seats])-([Statistical_Account].[Required_Seats])*
if i use *([New Seat Additions]+[Available_Seats])-[Required_Seats]* it is not veryfying throwing some syntax error
Thanks

Essbase ASO - How to aggregate all Parents in multiple dimensions when using member formulas

We are trying to add a few MDX member formulae on some of our Accounts in the ASO cube. We recently understood that member formulas in ASO calculate both LEVEL0 and Parent members of other dimensions, So we are trying to tell Essbase to calculate LEVEL0's only and to aggregate all other levels in all dimensions. However we are unable to get the syntax right. Below is what we so far have
AccA has below formula:
CASE WHEN ISLEVEL([Period].Currentmember,0)
THEN
AccX+AccY
WHEN ISLEVEL([Period].Currentmember,1) OR ...etc
THEN SUM({LEAVES([Period].Currentmember)},[AccA])
END
This does work fine and gives correct values for Parent members in Period dimension. But we also have 3 other dimensions like Product, Area and Entity. We tried the below but this throws an error during retrival.
CASE WHEN ISLEVEL([Period].Currentmember,0)
THEN AccX+AccY
WHEN ISLEVEL([Period].Currentmember,1) OR ...etc
THEN SUM({LEAVES([Period].Currentmember),LEAVES([Product].Currentmember)},[AccA])
END
Should we add multiple SUM commands in there? All we want to do is tell Essbase to aggregate all other dimensions to parent levels. Please help.

Sorry to reiterate the post again.
DanPressman Was wondering what would be other way to write calculations other than Accounts.
I have a case where the user wants to calculate Ending Equity and this should be calculated at level0 using the rates and all parents of entity has to aggregate.
1. Level0 of entities calculate with rates
2. aggregate its children to parent entity
I have used solve order to get it work but taking a lot of time.
Is there any other alternative way of doing it? Which other dimension i can choose to perform this calculation? This is exactly similar to productsum calculation

Converting Member Formulas to MDX

Hi Experts!
I'm converting member formulas to MDX for an ASO cube I created and I'm having trouble with the ones that use @MDSHIFT. I'm new to MDX and trying to learn as I go. One of the formulas I'm struggling with is:
IF( @ISMBR("Budget"))
(("Operating Results"-
(@MDSHIFT("Operating Results", -1, "Years", , 10,"Budget",)+
"Reclassification Operating Results"))/
(@MDSHIFT("Operating Results", -1, "Years", , 10,"Budget",)+
"Reclassification Operating Results"))*100;
ELSEIF( @ISMBR("Business Plan"))
(("Operating Results"-
(@MDSHIFT("Operating Results", -1, "Years", , -4,"Business Plan",)+
"Reclassification Operating Results"))/
(@MDSHIFT("Operating Results", -1, "Years", , -4,"Business Plan",)+
"Reclassification Operating Results"))*100;
ELSE
(("Operating Results"-
(@MDSHIFT("Operating Results", -1, "Years",)+
"Reclassification Operating Results"))/
(@MDSHIFT("Operating Results", -1, "Years",)+
"Reclassification Operating Results"))*100;
ENDIF;
This is for a change year over year % member. Any help would be much appreciated! Thanks!
-Cheers

In all honesty - it looks like you should not just 'convert it.' I dont see any real need to use MDSHIFT here. I would just use PrevMember function for years, while hardcoding the scenario into the tuple.

Attributes in member formula

I want to run a simple member formula but fix it on only entities that have a certain attribute: "Comp".
I have a BSO cube partitioned with an ASO cube with the following member formula:
================================================
In BSO:
IF("Received In Qty" > 0 )
@ROUND("Received In $" / "Received In Qty",2) ;
Else
#missing;
ENDIF
In ASO:
IIF(([Received In Qty] > 0),
ROUND([Received In $] / [Received In Qty],2),MISSING)
================================================
I need to have the member return the rolled up value of the entities that have the Comp attribute only.
So the logic in the formula would be something like this:
============================================================
In BSO:
IF(ISMBR(WITHATTR(Comp)) AND IF("Received In Qty" > 0 )
@ROUND("Received In $" / "Received In Qty",2) ;
Else
#missing;
ENDIF
In ASO:
IIF(IS(WITHATTR [Comp])) AND IIF(([Received In Qty] > 0),
ROUND([Received In $] / [Received In Qty],2),MISSING)
=======================================================================
The system doesn't allow me to save this due to syntax issues.
I don't want to pursue this if returning values for this is not even support.
Do you know how to do this. If it is a quick answer I would appreciate the help.
Thanks.

Wouldn't the fact you used the attribute in your retrieve affect the results of your query? I'm not sure if I am misunderstanding your requirement, but the formula is global, if you only want to see it applied to members with the attribute 'Comp', then run your report with that attribute selected.

ASO MDX query in outline??????

Trying to write a MDX query for the Account member
Hierarchy:
Account
A001
A002
A003
A008
Scenario
AG00
AG01
AG06
AG08
AG09
Organization
ETCE
E023
E024
E070
I need to caluculate for the Account AG08 the value should be derived from AG07 and for the same account AG08 for the Organization member "E070" the value should be same as AG09 ( i.e AG09 = AG08 )
I writen below query at the level "0" retrival query is good but when i use the Top level query "ETCE" parent level the value in "E070" is eliminating . Query writen below
NONEMPTYMEMBER [A001],[A007]
CASE
WHEN (IS([Organization].CurrentMember, [E070])) THEN
([A009])
WHEN (IS([Scenario].CurrentMember, [AG00])) THEN
(([A007] * -1)/100)
WHEN (IS([Scenario].CurrentMember, [AG01])) THEN
(([A007] * -1)/100)
WHEN (IS([Scenario].CurrentMember, [AG02])) THEN
(([A007] * -3)/100)
WHEN (IS([Scenario].CurrentMember, [AG03])) THEN
(([A007] * -10)/100)
WHEN (IS([Scenario].CurrentMember, [AG04])) THEN
(([A007] * -20)/100)
WHEN (IS([Scenario].CurrentMember, [AG05])) THEN
(([A007] * -80)/100)
WHEN (IS([Scenario].CurrentMember, [AG06])) THEN
([A007])
ELSE
Missing
END
At Bottom level "0" results are coming as expected but Its not working at the top level Organization ETCE level Please help ????
Thanks
Venu
Edited by: user13351102 on Oct 28, 2011 5:19 PM
Edited by: user13351102 on Oct 28, 2011 6:31 PM

Guru's any help on this ASO Member formula query ??

ASO MDX queries

Hi,
Is there any possibility that we can use semicolon at the end of MDX member formulas for ASO database? If yes please let me know how we can write and calculate member formulas with semicolon at the end?
One thingI know for sure is we should not use semicolon at the end of member formulas for ASO in admin console.

Syntax has changed for ASO member formulas and semicolons are no longer used. Why would you want to use the semicolon? With the new syntax it is not necessary.

Help needed in BPC 10 Member Formula

Hello Experts,
We are in BPC 10 NW SP 11.
Facing below error in report for Ratios hierarchy after
member formula is built.
Formulas is related to ratio
IIF([ACCOUNT_GL].[RE_IREV]=0, NULL, [ACCOUNT_GL].[RE_IAADJ]/[ACCOUNT_GL].[RE_IREV]);SOLVE_ORDER=10
RE_IREV is Income node
RE_IAADJ is expense node.
I have tried formula by removing square brockets for ACCOUNT
DIM member. Still no success.
Surprisingly, same formula, same hierarchy works fine in
another Model.
I have also compared measures in both the models, both are
identical.
Error in the report as below.
Server message:
code: UJO_READ_EXCEPTION_018
severity: error
description: MDX statement error: Value RE_IREV
/CPMB/WADNXJI for characteristic /CPMB/WADNXJI unknown
log id: KoFXP08mHM3X08002fJHZW
DATAVALUE: Value RE_IREV /CPMB/WADNXJI for characteristic
/CPMB/WADNXJI unknown
MDX: WITH MEMBER
[Measures].[PERIODIC] AS 'IIF([/CPMB/WADNXJI
PARENTH2].[2/CPMB/ACCTYPE]="INC",-[Measures].[/CPMB/SDATA],IIF([/CPMB/WADNXJI                 PARENTH2].[2/CPMB/ACCTYPE]="EXP",[Measures].[/CPMB/SDATA],IIF([/CPMB/WADNXJI
PARENTH2].[2/CPMB/ACCTYPE]="AST",([Measures].[/CPMB/SDATA],
CLOSINGPERIOD([/CPMB/WADBQQD
PARENTH1].[LEVEL02])),IIF([/CPMB/WADNXJI                 PARENTH2].[2/CPMB/ACCTYPE]="LEQ",-([Measures].[/CPMB/SDATA],
CLOSINGPERIOD([/CPMB/WADBQQD
PARENTH1].[LEVEL02])),-[Measures].[/CPMB/SDATA]))))' SOLVE_ORDER=3 MEMBER [/CPMB/WADNXJI                 PARENTH2].[RE_ALAE_RATIO] AS
'IIF([/CPMB/WADNXJI
PARENTH2].[RE_IREV                         /CPMB/WADNXJI]=0,
NULL, [/CPMB/WADNXJI
PARENTH2].[RE_IAADJ
/CPMB/WADNXJI]/[/CPMB/WADNXJI                 PARENTH2].[RE_IREV                         /CPMB/WADNXJI])'
SOLVE_ORDER=10 SELECT NON EMPTY {[/CPMB/WADBQQD                 PARENTH1].[2013.Q1                         /CPMB/WADBQQD]
,[/CPMB/WADBQQD
PARENTH1].[2013.Q2                         /CPMB/WADBQQD]
,[/CPMB/WADBQQD                 PARENTH1].[2013.Q3                         /CPMB/WADBQQD]
,[/CPMB/WADBQQD
PARENTH1].[2013.Q4                         /CPMB/WADBQQD]
,[/CPMB/WADBQQD
PARENTH1].[2013.TOTAL                      /CPMB/WADBQQD] } * {[/CPMB/WADNXJI                 PARENTH2].[RE_ALAE_RATIO]
,[/CPMB/WADNXJI
PARENTH2].[RE_ALL_RATIOS                   /CPMB/WADNXJI] ,[/CPMB/WADNXJI                 PARENTH2].[RE_COMBINED_RATIO]
,[/CPMB/WADNXJI
PARENTH2].[RE_EXPCOMM_RATIO] ,[/CPMB/WADNXJI                 PARENTH2].[RE_LOSS_RATIO]
,[/CPMB/WADNXJI
PARENTH2].[RE_OTHERCOMM_RATIO] ,[/CPMB/WADNXJI                 PARENTH2].[RE_STAT_COMB_RATIO]
,[/CPMB/WADNXJI
PARENTH2].[RE_STAT_EXP_RATIO] ,[/CPMB/WADNXJI                 PARENTH2].[RE_TOT_EXP_RATIO]
,[/CPMB/WADNXJI
PARENTH2].[RE_TOT_LOSS_RATIO] ,[/CPMB/WADNXJI                 PARENTH2].[RE_ULAE_RATIO] } ON
0 from
[/CPMB/WAMSZKS/!!O/CPMB/WAMSZKS]
WHERE ( [Measures].[PERIODIC] ,[/CPMB/WAD3OFZ                 PARENTH1].[ACTUAL]
,[/CPMB/WAD0VHV
PARENTH1].[ALL_CHANNELS                    /CPMB/WAD0VHV] ,[/CPMB/WAD021F                 PARENTH1].[LEGAL                           /CPMB/WAD021F]
,[/CPMB/WADME7W                 PARENTH1].[ALL_DATASRC                     /CPMB/WADME7W]
,[/CPMB/WAD0DZ0
PARENTH1].[FGI
/CPMB/WAD0DZ0] )
V1:Value RE_IREV /CPMB/WADNXJI for characteristic /CP
V2:MB/WADNXJI unknown
V3:
V4:
Thanks,
Senoy

Hello Vadim,
Thanks for the reply.
I am able to process ACCOUNT_GL dimension.
Also, I am using standard TIME dimension.
I found that the virtual provider(created by using source of data for my model) too is showing the error, when I place above member formula.
I am attaching the error messae when I try to do list records in the virtual provider.
When I remove the member formula, everything is fine
Thanks

Problem with member formulas and allocation

Hi guys,
I am experiencing a problem I am not currently able to solve. I'm building a planning application in which
volumes can be inputed in different units of measure (5 are currently available). For example a user can input in liter or KG, and the
system converts this data in all the different units of measure available, executing a script logic after
the input (for every bas member is also stored a conversion factor, which is used by the logic for conversion).
Two are the major issues of this approach:
1) storing 5 different volumes for every SKU is consuming in term of disk and DB space;
2) script logic must be executed every time the user sends data and in some cases this could be time-consuming.
The solution I'm trying is to use member formulas in order to calculate different units of measure, storing
only one of these. However, this way lead to another problem: when I try to input data with a top-down approach, using BPC
ALLOCATION ENGINE, I cannot use the correct unit of measure as a driver for the spread.
For example, if I input volumes is KG, and the unit of measure stored is only liter, I cannot use nor KG as a driver (because is not stored,
but only a member formula) neither liter, because the spread using this driver would lead to a wrong result.
What I would like to do is to give the user the possibility to input in the desired unit of measure at an aggregated level and spread data
using the existing mix, which must be volumes with the same unit of measure used for input.
Does anyone has an idea that could help me?
Regards
Edited by: utenza pubblica Public on Oct 23, 2009 4:48 AM

hi
i found a solution for the Problem in another Forum
http://businessintelligence.ittoolbox.com/groups/technical-functional/hyperion-admin-l/dynamic-calc-formulas-not-refreshed-1719379?cv=expanded
The suggestion is
1. change the Member from Dynamic Calc to Store
2. Refresh (After these Step the Formulas where still out of sync)
3. change the Member from Store to Dynamic Calc
4. Refresh
After these Steps the Formulas are in sync again.
Kevin Kraft
Edited by: Kevin Kraft on Mar 25, 2009 12:33 PM

Business Rule/Member formula for Y-T-D value

I have an account in my P&L which holds monthly movement values (e.g. Jan=10, Feb=20, Mar=10, Apr=15). Lets Call this AC123
I need to populate Balance Sheet account (TB Last) with the "Y-T-D" equivalent values (i.e. Jan=10, Feb=30 [10+20], Mar=40[10+20+10], Apr=55[10+20+10+15]. Lets call this AC345.
How can I calculate AC345 as Y-T-D(@CURRMBR(PERIOD))->AC123?
Currently I have a member formula on AC345 as follows:
IF(@ISMBR("Jan"))
     "AC123";
ELSEIF(@ISMBR("Feb"))
     Jan->AC123+Feb->AC123;
ELSEIF(@ISMBR("Mar"))
     Jan->AC123+Feb->AC123+Mar->AC123;
ELSEIF(@ISMBR("Apr"))
     Jan->AC123+Feb->AC123+Mar->AC123+Apr->AC123;
ELSEIF(@ISMBR("May"))
     Jan->AC123+Feb->AC123+Mar->AC123+Apr->AC123+May->AC123;
ELSEIF(@ISMBR("Jun"))
     Jan->AC123+Feb->AC123+Mar->AC123+Apr->AC123+May->AC123+Jun->AC123;
ELSEIF(@ISMBR("Jul"))
     Jan->AC123+Feb->AC123+Mar->AC123+Apr->AC123+May->AC123+Jun->AC123+Jul->AC123;
ELSEIF(@ISMBR("Aug"))
     Jan->AC123+Feb->AC123+Mar->AC123+Apr->AC123+May->AC123+Jun->AC123+Jul->AC123+Aug->AC123;
ELSEIF(@ISMBR("Sep"))
     Jan->AC123+Feb->AC123+Mar->AC123+Apr->AC123+May->AC123+Jun->AC123+Jul->AC123+Aug->AC123+Sep->AC123;
ELSEIF(@ISMBR("Oct"))
     Jan->AC123+Feb->AC123+Mar->AC123+Apr->AC123+May->AC123+Jun->AC123+Jul->AC123+Aug->AC123+Sep->AC123+Oct->AC123;
ELSEIF(@ISMBR("Nov"))
     Jan->AC123+Feb->AC123+Mar->AC123+Apr->AC123+May->AC123+Jun->AC123+Jul->AC123+Aug->AC123+Sep->AC123+Oct->AC123+Nov->AC123;
ELSEIF(@ISMBR("Dec"))
     Jan->AC123+Feb->AC123+Mar->AC123+Apr->AC123+May->AC123+Jun->AC123+Jul->AC123+Aug->AC123+Sep->AC123+Oct->AC123+Nov->AC123+Dec->AC123;
ENDIF;
But there MUST be a more elegant way to do this!!
Version 11.1.1.3
I hope the question is clear. Thanks in advance for your help.
Paul
Edited by: 973421 on Nov 27, 2012 3:38 AM

Hmm, well one way you might do this is to a YTD hierarchy (I know you are doing movements, but sometimes balances are nice, too, and this approach lets you TB whatever with the values and get the right YTD value) in my Months/Time Period/whatever dimension.
Something like this (and I am making it Planning-centric but should work for any BSO db that has separate Years and Months dimensions):
Months
|_TotalYear ~
|___Q1 +
|____Jan +
|____Feb +
|____Mar +
etc.
And then at the same level as TotalYear I would have this:
YTD ~ Label ONly
|_Jan YTD ~
|__Jan +
|_Feb YTD ~
|__Jan YTD +
|__Feb +
|_Mar YTD ~
|__Feb YTD +
|__Mar +
etc.
That gives you the YTD values (balance or movement) but you still need to refer to the correct YTD member and that means the big IF statement still exists.
What I think you need is the @CURRMBRRANGE formula:
http://docs.oracle.com/cd/E17236_01/epm.1112/esb_tech_ref/currmbrrange.html
NB -- This is a guestimate on your code, but how about this:
"AC345" = @SUMRANGE("AC123", @CURRMBRRANGE("Months", LEV, 0, , 0)) ;
The startOffset value is null -- that should give you Jan. The endOffset is 0, that should give you whatever the current Month is. I think that's it. I would likely make this member a dynamic calc but that's up to you.
Regards,
Cameron Lackpour

ASO: MDX Retrieving Last non #Missing Value.

Hi,
I am trying to create MDX.
I have data as follows:
Jan Feb Mar Apr May Jun
10 20 #Missing #Missing #Missing #Missing
Is the following possible, that every member of the time period is parsed, and if data found #Missing, the value is changed to last available value.
So, in the above example, I get Mar through Jun as value 20.
All help is deeply appreciated. Let me know if any further description is required.
Thanks.
Ankur.

At a fundamental level you would do something like
Create a member in your measures dimension called [Last_Sales]
add member formula
IIF((NOT IsEmpty([Measures].[Sales]), [Measures].[Sales], ([Measures].[Last_Sales], [Time].PrevMember)
Now this should work if you in fact encounter a value before reaching the beginning of the time dimension. If there is a chance no value will be found, this would error, so you will have to add more code around it to test for those scenarios.
This topic is covered in depth in Chapter 5 of George Spoford's book 'MDX Solutions'.
If you are going to be working with MDX, you should read this book.

Why does commenting out calculated member formulas in BIDs cause several minutes of CPU spike and non-responsive BIDs?

I'm using SQL Server 2012. I have noticed that commenting out calculated member formulas in BIDs (like even just 10 lines of formula) can cause BIDs to throttle all the CPU and become unresponsive for minutes. What could be the cause of that?

Hi Lee,
According to your description, you get high CPU usage when commenting out the calculated member formulas. Right?
With your information, we are not sure this is a MDX Query performance issue or the BIDS issue. We suggest you optimize your MDX query and diagnose the Formula Engine performance. Please refer to the links below:
Query Performance Tuning in Microsoft Analysis Services: Part 2
Analysis Services Query Performance Top 10 Best Practices
If possible, please post some screenshots or detail information about calculated member formulas so that we can have some deep analysis.
Best Regards,
Simon Hou
Simon Hou
TechNet Community Support

BSO member formula conversion to ASO MDX

Similar Messages

Maybe you are looking for