I've tried using the @xrange function, it's validating but it doesn't take into consideration the months in the next year: I need to get the sum of an element across different scenarios and years as mentioned below:
Do you have forecast then budget in your your outline? Months will go in order of the outline, which makes sense and is intuitive. I believe the other dimensions work the same way, it would take what is between Forecast and Budget. If Budget is not after Forecast, I am not sure it would understand what you are asking for.
Please make sure to assign helpful/answered to responses if applicable - it rewards those who help and benefits the user community.
Are you saying that if you did something like @XRANGE(ACCT, "Jan"->&V_BUDGET_YEAR->"Budget","Dec"->&V_BUDGET_YEAR->"Budget"), you would get nothing? I know this isn't your end goal, but if this doesn't provide you the data you expect, I would look at whether the variables have the right year and make sure data exists (I know you probably already have). If you change the variable value, make sure you restart the app.
Edited by: Kyle Goodfriend on Oct 11, 2012 10:31 AM
@LIST should accept any number of arguments and is used to add members together for another function that takes a list of members.
I think your Xrange is fine, it is the reference for your budget year.
If you just have @Sumrange(Acc_1,@Xrange("Jan"->&V_BUDGET_YEAR->"Budget","Dec"->&V_BUDGET_YEAR->"Budget")), what do you get? If you get 0, I would look at the variable. Update it in EAS (make sure you hit set so it saves), restart the app, and try it again.
The variable isn't new...it's referenced everywhere in the application..
I'm not trying the syntax you wrote for the xrange as it's within the same year and scenario...my xrange was trying to get from august this year, in forecast scenario...till december next year in budget scenario......which didn't return any number..nothing..
Is there any bug with the xrange function or any workaround to acheive the desired result ?
I am suggesting you try it JUST to see if you get any data. If you try this, and don't get any data, I would look to something outside the XRANGE function, like the data in the intersection you are trying to retrieve, or the variable.