About chenjack.sonos

Hi @varun.joshi07 Here's a quick and dirty way to get there - might be more efficient ways. This is also assuming you're working with months for a given year. ... 查看更多

Hi @tejaswini An alternative (though probably not a great solution) is to set the override as a text-formatted line item. When a user enters 0 into that line item, you can evaluate it in the 3rd line item with VALUE(x) to determine if there's a number there. Formula : IF ISBLANK(override) THEN initial value ELSE VALUE(override) This does not prevent users from entering non-numeric values, which will evaluate to NaN in the final value. This may be preferable if you're trying to alert the end user that it's invalid. However, if you want to default to the initial value, you can add an additional evaluation IF ABS(VALUE(override)) >= 0 THEN... This will check to see if the override evaluates to a number, and if it doesn't, default to initial value. ... 查看更多

For POST, I imagine it as posting an entry x periods before or after. From a logic evaluation perspective, if you look at the 6,000 in Feb 15, it's comprised of ALL POSTs that would hit Feb 15. Jan 15 posts 3,000 1 period later Feb 15 posts 1,000 in its period Mar 15 posts 2,000 1 period back Feb 15 would then aggregate all POSTs for that period. You wouldn't evaluate it as a siloed period - it's an amalgamation of all periods that POST to it. If Jun 15 had a POST(1000,-4), Feb 15 would then have 7,000 in its cell. ... 查看更多

Hi @johan.marketoft , It's best practice to use a saved view - please see the following article for more information: Data Hub Best Practices Best, Jack ... 查看更多

You can create a dummy model and set the Time Settings to Weeks. Create a module with Time as the dimension with a number formatted line item - set the formula to 1. This will sum up the # of weeks in a given month (see attached image). You can then import the months into your spoke model. Just a note: this is a workaround, likely not the optimal solution! ... 查看更多

Hi @Sampriti.Anand If I'm understanding correctly, you need the saved view to pull the latest year in your 3 year custom time range. Example, FY18-20, show 20; FY19-21, show 21. Here's what worked for me - there may be simpler ways, of course: Create a YEAR time module with the custom time range Add a boolean-formatted line item OFFSET(1, 1, 0) = 0. This will give you the latest year in the time range. Create a MONTH time module with the custom time range Add a boolean-formatted line item YEARVALUE(SYS Year.Time). This will bring the boolean to the month level. Apply the time filter on your target module for the saved view Let me know if that works! ... 查看更多