About rob_marshall

rob_marshall

@CommunityMember115881 Absolutely, very happy to and this is a question we get a lot. TimeSum is not meant to be used when the target (where you are doing the timesum) has Time in the Applies To Now, that doesn't mean it doesn't work because it does, but it adds additional overhead that is not needed. Check out this video @MarkWarren and I put together last November. https://www.youtube.com/watch?v=PvimWuX5jVw Hope the helps

rob_marshall

@andre.lie @CommunityMember123764 Please do not use TimeSum when the target (the line item containing timesum) is dimensionalized by Time (Time in the Applies To) as this is a huge performance hit. Instead, consider using MovingSum(). Link on MovingSum Rob

rob_marshall

@ShekharGite To play Devil's Advocate, why would you have multiple people updating the exact same cell or intersection of data? Rob

rob_marshall

@gaurav We see this problem quite a bit and my suggestion is to work backwards to forwards, meaning from reporting requirements to development of modules and logic. I say this because from the beginning, you stated it will be many modules needing these versions and snapshots, but is that really the case? I would suggest understanding what the true requirements are for reporting and variance analysis and then define the modules/logic for that. When you do this, you very well may need a few modules with all of these versions, but not likely for all of them from a reporting perspective. Also, another idea, you might want to consider mixing native versions (for input) with a custom version list used for reporting. You may already know this, but bulk copy can be used on any list, not just native versions. Hope this helps, Rob

rob_marshall

@brettnish May I ask why are you needing the tenant ID? I am not sure that is available if you are not a workspace admin. But, if you need a workspace ID (this is really all you need) or model ID, you can find that in two places: in the address bar or click the Help and select About

rob_marshall

@CommunityMember122229 So, in that module, are you going to dimensionalize the module by Users? What exactly are you trying to accomplish with this line item being User? Can multiple people update this module? Can Selective Access be used so only certain people update it or is more of who updated it last? If it is the latter, then you will most likely have to have an action to update that line item with User in it. Rob

rob_marshall

@CommunityMember122229 The User is implied. Take a look. Create a module with data Create a DCA module with two line items, Read and Write as booleans Go back to the original module, and enable the DCA pointing to the DCA module With write enabled, I can see the data Removing the Write boolean I no longer see the data, no lookup needed Hope this helps, Rob

rob_marshall

@DeveloperCYT Did you try using YearValue? This assumes you don't want to span the year which I believe your MovingSum does since it is a rolling time period. Again, happy you figured it out, I was just wondering if this alternative way would have worked for you. Rob

rob_marshall

@DeveloperCYT Well done...Quick question, instead of using the MOVINGSUM() function, could you just enable the summary for FirstNonBlank? Rob

rob_marshall

@suruchi.kapoor Yes, it will work for Outlook as well as Windows.

rob_marshall

@Misbah You are correct, I think this is my 3rd straight year. And yes, what a great group to be part of.

rob_marshall

@dameyer01 Well Played!!!

rob_marshall

@dameyer01 Yes, you can absolutely do a finditem() on a subset as it is just another list. But, in changing the Applies To to the subset and just entering TRUE, that will be much faster, especially on larger lists. Why, because something that is hardcoded to TRUE is way faster than going through a list and looking at the member and the code, which is what a Finditem() does. Rob

rob_marshall

@Shradha Which role is running the action, an administrator or someone with specific roll access (Not Full Access)? I ask because if the person does not have full access, DCA is still observed while if an admin, the DCA setting is not observed. Rob

rob_marshall

@swapnil_J I totally agree the action should not prompt the user when importing which is what I stated: First, it is really not best practices to have endusers upload files to a production model because: could possibly lose data integrity data can no longer be audited back to the source (user can manipulate/change the data before they upload it) when a user runs an action, it blocks the model for input by others, so now there could be a concurrency issue Second, when a member or metadata is loaded, the member has to go into a list first and then the supporting metadata or transactional data goes into a module. So, if you are importing a new member to the list and then want to load supporting information to a module, you can do that with two actions: load member to list load supporting data to module. By doing that, it will only load the data from that one file. Rob

rob_marshall

@SudhirY Yes, I do see issues with what you did. because you are nesting the NEXT function and making Hyperblock work harder for every calculation. Instead, I would break it up and do this Create two line items: Previous Year/Previous Quarter mbr:'Current Period' - 5 (formatted as Quarter) Previous Year/Previous Quarter?: item(time)='Previous Year/Previous Quarter mbr' (formatted as Boolean)

rob_marshall

@SudhirY You can do this in two modules, one for Quarter and one for Year. First, make sure you Current Period is set in the Time Settings The module for Quarter should be only dimensionalized by Time (a SYS Time - Quarter module) at the Quarter level. Create these three line items: Do the same thing for Current Year Now, you can create a module to use your DCA basing it off these values. Rob

rob_marshall

@ChrisHeathcote Yep, agreed. It is a possible solution, just not a good one if there are many line items with logic you want to "hide". Another possible solution, and it is in line with the previous one, but to have a "reporting" module where the line items are just "dummies". Think of the logic as a CALC module and then you have the reporting module just referencing the calc. Might be too much of a hassle, though. Rob

rob_marshall

@vazqulu1 I think you are very close. Take a look at this: I have a list with a subset define: In my SYS Invoices module, I have a line item with the Applies To being the subset. Line item is formatted to Boolean with the formula being True. When I exit the blueprint, since ss_Active: Invoices (the subset) is part of Invoices, it will show a check for the members that are in the subset Also, doing it this way versus doing a finditem() is better for performance reasons. Looking at your formula, it looks like the subset is on L4 but you are doing your finditem on L5. If this is correct and L5 rolls up to L4, then you will not be able to find it as the subset doesn't go down to L5. So, if L4 is a parent of L5 and the subset is on L4, then create a line item on L5 (formatted to L4) with the formula being: parent(item(L5)). Then you can do a lookup to the L4 subset: SYS L4.Subset?[lookup:the line item for parent of L5] Hopefully, that is what you are looking for Rob Rob

rob_marshall

@egc8r And can you confirm the decimal places for that line item is not set to 0?

rob_marshall

@JBeauchs Basically, you are trying to accomplish a calculation that you are wanting to do sum of data on and the calculation can't do it. Usually, this means you are missing a Top Level member of a list (which is used to get a total of that list). For example, if I have a list of Employee's without a top member, Rob Mark Jeff George Well, there is nothing at the top to sum that data. To fix that, put in.a top level member in the Configure tab of the list All Employees Rob Mark Jeff George

rob_marshall

@ChrisHeathcote I don't believe so, but possibly create a dummy line item that is just the result of the logic and base the downstream calcs off the dummy? Rob

rob_marshall

@AdamE I found the same thing as you...Try this, it worked for me: Basically, I changed the the following: Cumulate to: To or Next(Cumulate To) Final: Cumulate From and Cumulate To

rob_marshall

@Suchou You can find it here https://community.anaplan.com/t5/Releases/August-2020-Releases-and-Sneak-Peek-at-September/ba-p/82366 Granted, not too much information on it, just that it was released in August.

rob_marshall

@Suchou I am very sorry to say, but David will not be responding as he has left the company for another opportunity. With that said, you can find more information here: https://community.anaplan.com/t5/Platform-Updates/ct-p/Releases Rob

rob_marshall

@ChrisHeathcote It depends. If they are wanting to sum the values for all of time, then timesum() without the Time in the Applies To is the way to go. The last part is the key! If they are wanting to sum only the monthtodate quartertoDate, or YearToDate, then use those formulas. If they are summing between two dates and the line item has Time in the Applies To, then MovingSum() is the way to go. Rob

rob_marshall

@anirudh @kevin.cho is correct, there are three different settings, 30, 60, and 90 days and is set when the workspace is first created. This can be changed by support at the request of the tenant admin. Rob

rob_marshall

@ChrisHeathcote @shrey_meher For optimal performance, try breaking that calculation up so it is not doing all of the cumulates for the line items for every cell in this line item. Also, when any of those line items change (Revenue, Fixed Rent, Var Rent, or Total Revenue) change, this entire logic gets kicked off (for ever cell of this line item) which is why breaking it up it much better from a performance perspective. Additionally, in the above, you are doing a cumulate of Fix Rent multiple times. Again, if you break this up, you are only doing it once. Rob

rob_marshall

@ChrisHeathcote Please don't use TimeSum when the line item is dimensionalized by Time, that is a massive performance hit. TimeSum() should only be used when the source is dimensionalized by Time, but the target (result) is not. In case you haven't seen this yet, please check out this youtube where Mark and myself have a little fun explaining this. https://www.youtube.com/watch?v=PvimWuX5jVw Rob

rob_marshall

@AWhitworth While this does work, it is best to create a unique ID at the source to remove extra processing time and work by Hyperblock. Also, by creating the unique member at the source, you will be able to import the transactional data to Trans module and the properties to a SYS Properties module. If you use the combination of properties method, you will not be able to do that and will be forced to store all data as properties in the list which is not advisable and is against best practices. Rob