About Jared Dolich

Hi @avinash_rai . There are two ways you can achieve this.   You can create a system module (see the DISCO methodology, "S") with one line item and no dimensions. There you can enter the current month. In your other module where you need the Boolean you can lookup the line item in the system module. I highly recommend reading @DavidSmith article on DISCO. One of the best posts on the community site. https://community.anaplan.com/t5/Best-Practices/Best-Practices-for-Module-Design/ta-p/35993   Another way you can do this is to refer to the current period. CURRENTPERIODSTART(). this will return a date. Since you need a month, you can add the PERIOD function to that.  PERIOD(CURRENTPERIODSTART()).   Generally speaking, best practice is to create a system module for time attributes like this. "Calculate once, Reuse Often". You might consider moving your Boolean to a system module and look it up when you need it instead of putting in your output module.   Hope this helps.   Jared ... View more

@kdoan There should be a choice for line items when you go through the mapping. This will allow you to apply a dimension to a row header. I've never tried to import multiple dimensions so you may have to break that up into to loads. ... View more

Thanks @DavidSmith. I've been using the Tabular Multiple Column when I have more than 3 dimensions for export out of Anaplan but I never considered it for a module to module import.  I'm going to give that a try. Is there a reason why we can't use a boolean filter on the time dimension? I have a client that wants to module to module import but only unelapsed days. I haven't found a good way to do that since there are 4 dimensions: date, 30 minute time increment, product, and partner. Because I have to import all days it's quite a big module 6GB and takes 25 minutes to import all that data.   Incidentally, this would be a great topic for the modeling cert 3.  ... View more

David, something we learned in the modeling certification 2 was to make sure the common dimensions are in the same order so the hypercube indexes them efficiently. Will this be a factor when importing from module (saved view) to module (target) or does this only apply to line item formulas? If so, how do we know if the saved view is in the right order? ... View more

Here's an example which also demonstrates the PLAN methodology and DISCO.   First we create a flat list from our structured list that only contains that hierarchy level. In this case we'll focus on the the subclass, our lowest level (this could be your department in your example)     Following DISCO, or the "S" for System, we create a system module using only the flat list we just created. This will contain all our booleans for filtering and for nested IF statements. In the PLAN methodology, this would be the "P" for performance and "A" for auditing. Notice we create all our booleans here, even the complicated ones. "Calculate Once, Reuse Often"     Here are the formulas for our system module. Very simple, concise, and easy to understand what they do. Lastly, we create an Output module, or "O" in DISCO. Several things to note here: - The nested if statement is very understandable "A", and uses the booleans from the system module. Very fast ("P")! - Always set up your IF statements to calculate the most likely scenario first. For example, most of the subclasses for our sales for the C and W less Swim sales (below) will meet this condition, so we test for that first.   Hope this helps! ... View more

I would strongly suggest you build a system module for departments and use booleans in your calculation. Check out the DISCO methodology.   This will make your if statement easier to read and be more efficient.   For example, you would create a system module for your department list. Only departments would be in this list (so make it flat - no parents or descendants). Then add line items that help you filter the departments. For instance, if the department code is less than 5999 then "TRUE".    Lastly, it is recommended that if you have a lot of IF, Then, Else, nested together you break them up.    Let me know if this is enough detail. I can create an example for you. ... View more

Agree with @NoahJ . It's really hard to see the READ/WRITE/NONE at a glance. Great idea.   ... View more

@Panji  I was going to say the same as @ankit_bhargava. I also believe you need to be a workspace admin in both workspaces.  Make sure you have that level of access. ... View more

Great idea @CallumW ! ... View more

Straight forward, simple. Great idea. ... View more

Agree. I use the notes section for each action to document the source & saved view but that's not very reliable especially if someone forgets to update the notes when they change the source or view. Great suggestion! ... View more

Brilliant. ... View more

@a.dilieto is right.  Just try to avoid line items that use sum and lookup in the same formula. These are not very efficient formulas. If you use the DISCO methodology, which is highly recommended, the parent lookup should be in a system module. "Calculate once", "Reuse Often". In this example "division" is in the same module but really belongs in a system module.   ... View more

Great idea - I can imagine some nuances with the dimensions being used though. And, assuming security will be taken into account.  ... View more

Is that a new function? This will save so much time! Thanks for sharing that. ... View more

Great idea for auditing. ... View more