About ChrisHeathcote

ChrisHeathcote

@Epratt The course will have asked you to update the summary settings for that line item. Review the course content and update the summary settings in the module blueprint.

ChrisHeathcote

@rps98 A few points to help you think through the query and hopefully lead you to the correct solution. It is not possible to combine YEARVALUE() and LOOKUP() in the same formula LOOKUP takes a grid dimensioned by the target list and lookups up another dimensions via a line item. This line item must be list formatted. LOOKUP does not work with text formatted line items as text is meaningless. Good luck

ChrisHeathcote

No. BLANK is not a valid entry for a number formatted line item. However, you may be able to us NaN which is 'Not a Number' to give you the same result. Use =DIVIDE(0,0) as part of an IF THEN ELSE function. Be mindful that you will see NaN as the result so may not be the ideal solution if the line item is to be presented to an end user.

ChrisHeathcote

Are field cards not designed to facilitate data input? Do the line items LOOKUP the second table?

ChrisHeathcote

You will need to create a mapping that bridges the difference in dimensions in the same way you would between two modules. The module has; Measures, P5Material, G2 Region The line item has; Measures, P1, G2Region However, assuming that P5Material and P1 are part of the same hierarchy and P1 is a higher level then the line item will simply take the value from the module which relates to the P1 layer. If they are not part of the same hierarchy then you will need to build a mapping table. If multiple P5 items map into a P1 item then create a mapping table dimensioned by P5 and add a line item formatted as a the list P1. Then use SUM. If its a 1 to 1 mapping then you can create a mapping table dimensioned by P1 and a line item formatted as P5. Then use LOOKUP.

ChrisHeathcote

@nildutta This is a frustration but as @abhay.kanik has already stated it is because your filters are not dimensioned by the user list. Currently the view will update for all users irrespective of who changed the filter criteria. Therefore, to confirm the change you need to manually refresh the page. To overcome this add the user list to the filter selector. Create a new system module which also contains the user list and the list to be filtered. Apply the filter as usual and allocate current user setting to the user criteria. Once this is complete the grids will update automatically without the need to refresh the page.

ChrisHeathcote

@abhay.kanik Yes, you are right. The solution will only provide whole numbers.

ChrisHeathcote

@algrigore How about =YEAR(Today) - YEAR(Birthday) Its a little simpler than the solution offered.

ChrisHeathcote

@Baddalwarvaibhav It is not possible to combine two process from different models.

ChrisHeathcote

@dominic.literal If you are looking to limit access to certain products by user then use SELECTIVE ACCESS. This tool will allow you to show and allow write access to certain parts of a given hierarchy or list by individual user.

ChrisHeathcote

@DMManalili If you are not use Current Period then you can LOOKUP the average and post this forward. For this you will need to create a module containing no dimensions or time. Add a time period formatted line item and use this to inform the LOOKUP.

ChrisHeathcote

@DMManalili I assume that there is a cut off point from which you want all future periods to be populated with the three month average. I will for this post assume that you are using current period. If so you can use =IF ISCURRENTPERIOD(END()) THEN MOVINGSUM(Commission %, -2, 0, AVERAGE) ELSE PREVIOUS(Previous 3 Months Average (Comm%)) However, I would recommend that you use a time system module to query the Current Period as this will be useful in other formulas.

ChrisHeathcote

Ok You will need to use the ratio summary method. Create two line items that calculate each side of the ratio and use these to populate the ratio settings. The two new line items should both be set to sum.

ChrisHeathcote

Makes sure the summary method is formula not sum.

ChrisHeathcote

@JoannaAn Break the formula out over several line items. Volumes Prior Volumes Growth You can also use an IF THEN ELSE statement to populate month 1 for Prior Volumes =IF PREVIOUS(Volumes) <> 0 THEN PREVIOUS(Volumes) ELSE Volumes This makes the assumption that this is the first month so closing volumes equal closing volumes. It Also assumes that every other month with have volumes greater than zero. If this is not the case then use @JaredDolich method of populating month 1. Also, remove the * 100% and simply format the line item as a % in the blueprint.

ChrisHeathcote

@eway I have a solution but there are a number of steps. The principles I followed here; Take the start date and add a number of days to create an end date Apply a series of queries against that end date to create an end date adjustment Weekend Holiday Add the adjustment to the end date to arrive at a final end date The following screenshots should take you through the various modules and line items. Where the formula is too large I have included individual screenshots so you can work through them in full. First here is the summary module where the user will enter a start date and a number of business days reference Secondly, here is the calendar module where the adjustment is calculated It is not necessary to create a fake time frame using a numbered list as I think has already been suggested. Using fake time should always be the option of last resort as you have already pointed out all the time functions are then redundant. Good luck

ChrisHeathcote

First thought - are you referencing another version using SELECT where you are pulling data from one version into another? Would be interested in hearing how this query get resolved!

ChrisHeathcote

@DarrenS Click on the table icon at the top of the column. By creating a line item that has different dimensionality to the master module you have create what is called a 'subsidiary view'. You need to apply a filter to the first module and reference this line item in the criteria. The link in the previous comment will take you through the required steps.

ChrisHeathcote

@DarrenS There is a user list so that the outcome of the selection will be user dependant. Without it all users will see the same outcome. The following link will also give you a good intro into filtering in Anaplan https://help.anaplan.com/5c7d1754-29cf-4861-a369-69c8fe0c31a1-Filter

ChrisHeathcote

@DarrenS It is a common error to include the dimension of the target line item in an attempt to add a filter. This will simply increase the size of your module by a factor equal to the number of items in the list. Follow these steps to set up your filter; 1. Create a module dimensioned by the list occupying the rows section of the pivot and Users. 2. Add a line item and format this as the list which will form the criteria of your filter (Account Type). Populate this line item in a similar way to the target module, TEST. 3. Add a boolean line item and name this 'Filter'. 4. Create a second module containing the user list only. Add a list formatted line item of the list you would like to base your filter on ( Account Type ). We will call this module 'Account Type Selection' and the line item 'Account Type Filter'. 5. Back in the first module add this formula to the boolean line item =AccountTypeSelection.AccountTypeFilter = Module1.AccountType This should generate a TRUE boolean for all items whose Account Type property matches the item selected in the filter module. 6. In your target module apply a filter, select the filter module and line item. Ensure you use 'Current User', to define the user dimension. 7. Save as a different view and publish to a dashboard along with the line item used in the Account Type Selection module.

ChrisHeathcote

@Suman Reddy Select the relevant dimensions, then select the eye icon. You can then select which items to show.

ChrisHeathcote

@DarrenS A page selector or dimension is not a filter. Can you raise this as another query and I will provide a more detailed response.

ChrisHeathcote

@Suman Reddy Yes

ChrisHeathcote

@ClarenceA Check the summary methods for all inputs are set correctly. Using average instead of formula as an example can skew the numbers. If your totals are reconciling but individual items are not then this indicates your mapping tables are complete but may have small differences. It may be prudent to import these again and double check. Good luck

ChrisHeathcote

@afdelarosa & @Suman Reddy Column width can be adjusted manually in the UX by selecting the edge of the column header and while keeping the button selected moving the selection left or right.

ChrisHeathcote

@dsoomar002 @JaredDolich What solution did you come up with?

ChrisHeathcote

@HaddoxCommunityAccount @CaitlinHester I can provide some general guidance but I can not give you the solution as you need to work through this test independently. LOOKUPS require a list formatted line item and it is through a lookup that you direct the formula to the correct dimensions in the source data. Changing the format of a line item is a destructive action and will result in all data entered against that line item being lost. These are two items of guidance which should allow you to both solve the issues you are experience. Good luck

ChrisHeathcote

@DarrenS How many L3 sit under Asia? It is possible to reference child text entries at the parent level but there are limited options. Notice that for TEXT the options relevant to you would be FIRST NON BLANK or LAST NON BLANK. These options will summaries up the hierarchy showing the text occupy the corresponding cell. However, this will continue up the hierarchy through L1. Using summary methods may not be the best way to show the cell contents at higher levels but if you are determined to show the data at L2 and above in the same module it is your only option. There is no current workaround for text alignment in a cell.

ChrisHeathcote

@Wolf37 An alternative solution would be to use an action to import the value from one module into the other only when the result of the IF THEN ELSE is TRUE. This would break the circular reference and allow you to transfer the values between modules. The circular reference is due to the use of the common dimension. From the screenshots you have provided the list is redundant and the same outcome could be achieve if you simply used line items.

ChrisHeathcote

@ClarenceA You are indeed correct in that a LOOKUP will only work when the lookup line item is a list formatted item. However, you could use MIN summary method and then SELECT to reference the top level of the product list. This may have been a simpler solution!