Hi Gurus!
Miss all of you!
I have a quick question about using @CurrMBR function in member formula.
Firstly, I am aware of that if I use @Currmbr in member formula for a Dense dimension member, it requires a longer time to retrieve data and may cause some unexpected issues.
Secondly, the idea is in Period dimension, say we have a member named "SUM" and data should be: prior year Dec + current year Jan
If I use:
IF(@ISMBR(FY16))
"Dec" -> @MEMBER(@SHIFTSIBLING(FY15, -1)) + "Jan";
ELSEIF(@ISMBR(FY17))
............
............
............
ENDIF
This way is all good.
But If I use: @SHIFTSIBLING or @PREVSIBLING and use @CURRMBR because I don't want to specify years, like:
"Dec" -> @MEMBER(@SHIFTSIBLING(@CURRMBR("Years"), -1)) + "Jan"
The issue is, if I use this way, after refresh database, go back to smartview, when I refresh it, it will pop up a window saying " It is an invalid form".
So I am just wondering since the validation is good, why I still see this error? Was my syntax or logic wrong, or this is because the @Currmbr is using for a dense dimension member may cause some issue that we cannot see?
Thanks in advance!
Regards,
Jun