About 1454884

I really appreciated this piece. I often think of how much of a time suck and a mental drain diving into comment conversations can be. But sometimes it is worth it. At the end of the day, it's important to assert oneself and to attempt to have discussions about what matters to you.   My CC Pay ... View more

@1454884    This can be done, but it will depend on the number of users that will be using this functionality because you will have to dimensionalized the output module by Users (if all of them will be using it) or by a custom list (Fake Users) if it is only a subset of users.  The reason I bring this up, you can very quickly blow up your model space if you have a lot of users using this functionality.   The top part or selection piece is what the users can filter on and are flat lists.  The bottom is automatic (summed) results of what was selected.       Basically, create modules based on the attributes you want to filter on, these modules are dimensionalized by that attribute flat list and User or Fake Users.   Create a module dimensionalized by your Materials and your Users/Fake Users with attributes as line items (boolean formatted).  This is comparing the attributes on the Materials list with what the users entered above.     My "Final Result"  is not like yours, yours needs to be a boolean with the formula (Credit? AND DQ? AND FICO? AND Method?).  You will use this for your filter.  Also, add another line item for the Amount which is linked to your original Amount in your Materials module (this does the dynamic subtotalling).   Let me know if this works for you and if you have any questions.   Rob ... View more

This a very critical requirement from many business users as they analyze based on different criteria and look at summaries filtering the grids based on this criteria. ... View more

Hello @tflenker and @abhaymalhotra  This post directly answers the question we raised about concatenating the key for transactional data in the DH. Also, read @rob_marshall article about the datahub (particularly the sections under:   Transactional Flat Lists Loading Data vs. Using Formula’s in SYS Modules Exporting to Spoke Models ... View more

@1454884    Only bring in the data at the level (granularity) you need into the spoke models.  So, if you have transactional (daily level) data in the hub but only use Monthly level data in the spoke model, only bring that into the spoke model.  Understand what data you really need for that model and what granularity and only bring that in.   Rob ... View more

@1454884    Great Question. It indeed impacts performance if we load the data over and over. We should  not load anything into Anaplan that has not been changed since the last load into Anaplan. Then what do we do in such cases. Here is the answer   You can do it in multiple ways From the source system, request IT to only send the updated information, not the full load every time. Additionally, request IT to create a column in the source file with a hardcoded value of “TRUE.” This will tell Anaplan which row is new or has been updated and can be used as a filter for an export. Just know, before the import of the source data gets loaded, make sure the first action within the process clears out the previous true records (set this up via a view using a filter where the view only shows members with a value of true). Utilize the current period function to only load the current period data. In the SYS Time Filter module, create a line item named Current Period with the formula CURRENTPERIODSTART(). In the export views  into Spoke model from Hub, filter the data on this line item. Hope this helps Misbah ... View more

Hi @1454884, I do not think that I saw apps available yet. I believe you could contact your Partner Success Manager to see if they can provide any examples. You can also now see Level 1 training in User Experience as well: https://learning.anaplan.com/course/view.php?id=1289 ... View more