![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
#3
| |||
| |||
|
|
A couple of issues to consider: - It seems that the ClosingPeriod() is superfluous in [OutstandingPrincipalPrevMonth], because the other code assumes that [Transaction Dates].CurrentMember is already at the day level (not sure if that's a valid assumption) - Even at the day level, [Transaction Dates] .currentmember.parent.parent.prevmember.lastchild. lastchild will not work as expected: start with June 15th. Initially, it evaluates May 31st, but if that's empty, the next recursion will evaluate April 30th, not May 30th. - Deepak Deepak Puri Microsoft MVP - SQL Server *** Sent via Developersdex http://www.developersdex.com *** |
#4
| |||
| |||
|
|
Hi Deepak, Thanks for your reply . 1. I understand that theres no need to use Closing Period() Function 2. How to apply CoalesceEmpty() for getting correct Balances starting for Current Month as well as starting for Previous Month in the Same Recursive Manner when i have one Transaction Date (at Day Level ) in my where Clause(Slicer) of MDX Query. Thanks again. Please tell me a possible solution . Deepak Puri wrote: A couple of issues to consider: - It seems that the ClosingPeriod() is superfluous in [OutstandingPrincipalPrevMonth], because the other code assumes that [Transaction Dates].CurrentMember is already at the day level (not sure if that's a valid assumption) - Even at the day level, [Transaction Dates] .currentmember.parent.parent.prevmember.lastchild. lastchild will not work as expected: start with June 15th. Initially, it evaluates May 31st, but if that's empty, the next recursion will evaluate April 30th, not May 30th. - Deepak Deepak Puri Microsoft MVP - SQL Server *** Sent via Developersdex http://www.developersdex.com *** |
![]() |
| Thread Tools | |
| Display Modes | |
| |