About ChrisHeathcote

ChrisHeathcote

Hi, You can create a line Item subset and create a filter module dimensioned by it. Using a boolean line item you can select which line items to show. However, this will only work for number formatted line items.

ChrisHeathcote

@soumyarani Hi, If you are based in the UK or Germany I can out you in contact with someone who will be very happy to run through the different features of both platforms and offer personal advise as to which is most suitable for you. Thanks, Chris

ChrisHeathcote

What is the calendar setting of the module in which the line items sits? If you are using a time range just for the line item while the overall module time frame is set as the calendar time this may be what is causing your problem. In the UX you allocate the module to the field card and I suspect that the module settings are then applied universally to that card.

ChrisHeathcote

@cpalm Create module dimensioned by the child. Create line items including parent (parent list format ), date ( date format ) and phasing ( number format ) Use the following formula for the parent line item =PARENT(ITEM(CHILD LIST)) Allocate the associated date to each child item. Set the summary method to Min. Use the following formula in the phasing module = IF date[LOOKUP:Parent] = date then 1 else 0 This will allocate a 1 against the child item whose date matches the min summary at the parent level. You can then use this to phase the parent value down the child in a target module dimensioned by the child list. Be mindful that if you have more than one child item with the same date you will duplicate the phasing across multiple child list items.

ChrisHeathcote

@CommunityMember113484 Sadly I do not think this is possible via the UX or modelling environment. However, I would explore using the add ins for Excel where you can create a dynamic link into your model and have the Excel update directly within Excel.

ChrisHeathcote

@MaartenGijbels Eliminate the circular reference by using the base data in all your calculations and avoid daisy chaining! Therefore, each time you need to reference a cup of coffee create a formula which takes the core ingredients rather than the outcome of the cup of coffee calculation.

ChrisHeathcote

Create a system module for you LISS and reference the full list directly. Use the selection in the LISS properties module to inform the delete action.

ChrisHeathcote

Therefore, you need to create a mapping from module A row_num to the list which forms the dimension of module B. Reference module A from module B and lookup this mapping to pull the data across. Without a dimension in module B and the mapping there is no way to establish the relationship between modules and therefore the mapping required.

ChrisHeathcote

@mohitveer_sandhu From your query I will assume that module A contains id as its dimension and module B name. If this is the case you need to create a mapping module dimensioned by name so that you can map each list item to a correct id. Once you have this the formula would be =module A.key2_value[lookup:Name mapping.id]

ChrisHeathcote

@Gayatri2020 You provide little in the way of detail but if you are not returning an error then I suspect your modules are not aligned across time dimensions. Please provide more details and I will be able to help further. Chris

ChrisHeathcote

@rob_marshall I wouldnt normally advocate loading time into a list property but to create the report @sreeharikv is looking for then I think it would be the simplest solution. However, I acknowledge that it is not best practice to load data into list properties and the combination of properties feature for a numbered list should only be used to create the list code. If the user is comfortable viewing the report as a series of nested rows then @rob_marshall is correct in his solution. However, be mindful that you are unable to nest more than three dimensions in either rows or columns so if you need to view more then a combination of approaches may be more suitable. Good luck.

ChrisHeathcote

@sreeharikv I would start by reviewing how you are importing your data. By using multiple dimensions in the import you are creating a significant amount of sparsity as it is very unlikely your data will be relevant across all intersections of the various dimensions. Redesign your data import to come into the model as a flat file. To do this use a numbered list and import your data using a combination of text formatted properties so that you can create a unique code. I would suggest from your query that you need to combine the following; Location, Lot#, available quantity and time. If still you have duplicated across these properties you will need to add more properties. Once you have your data in a list create a data module dimensioned by your import list and pull the properties into the module using FINDITEM to convert them into list formatted line item. Filter this module by a time filter set to show the current period. There is a lot of moving parts here. Let me know where you need further clarity. Chris

ChrisHeathcote

Create a new line item to hold the value for all departments and remove departments from the applies to. Reference your source data and the formula will take the top level / All Departments as a default.

ChrisHeathcote

Hi, I was asking to see examples of a schema not the actual L3 schema as it was not clear in the description or the training how they should look. However, I have now completed that part of the training as I developed my own style which I feel meets the criteria well.

ChrisHeathcote

As you target module is not dimensioned by meeting you need to direct the formula to the required meeting dimension. In circumstances where there is not a relationship between dimensions that you can use to map I recommend that you create a model LOOKUP module. These modules contain no dimensions and ONLY list items. Create a list item for the dimension you wish to lookup, format it as the required list and select the list item from the available options. What you have now is a list formatted line item that you can now use in a LOOKUP function in your target module. Now when referencing the source add the following to the end of the formula [LOOKUP:Lookups Module.Total Product A] This will inform Anaplan that you what to only pull data across which is at the intersection of Total Product A. If Total Product A is the parent of the items above you will need to format your lookup line item as the parent list.

ChrisHeathcote

@neg177 You will need to create a list for your weekdays and allocate the number from the WEEKDAY function as its code. Mapping the result of the WEEKDAY function to the list code will enable you to return the required list item / weekday. The link to Anapedia - WEEKDAY

ChrisHeathcote

@johan.marketoft This is possible but you need to create a few system modules that help you build up the logic behind the code. Create a system module dimensioned by the Process lists and a line item called code formatted as text. For each process define the first half of the employee code. Create a system module for the employees list if you do not already have one and create a line item formatted as the 'Process' list and one called 'Count' formatted as number. Create a staging module dimensioned by 'Employee' and 'Process,' containing a single line item called, 'Count.' Formula =Employee System Module.Count[Sum:Employee System Module.Process] Create a list called form entry and add one list item called, 'New Employee.' Create a module dimensioned by the list from step 4 and create line items for all the fields used to define the details of the new employee. We need Name, Process and Code as a minimum. The formula for code = Process System Module.Code[LOOKUP:Process]&TEXT(Employees Count Staging Module.Count[SUM:Process] + 1) This will sum all current employees in that process and add one. Use this module to import into the Employee list, using the Name field as the Display Name for your numbered list and the calculated Code.

ChrisHeathcote

@Rajasekhar The simplest approach here is to use the FINDITEM function. This takes a text formatted line item and then searchs a list for that Item. If the list item corresponding to the text is present in the list it will return that list item. Use this following link to the Anapedia page to go through the steps involved in setting this up FINDITEM Link If you still need to show the 'Exist,' or 'New' message you can use the following formula, =IF NOT ISBLANK(FINDITEM(List, Text formatted line item)) THEN Exist ELSE New Ensure that your target line item (line item 2) is formatted as text as the answer to this formula is text formatted. Chris

ChrisHeathcote

As has been confirmed pop ups is not currently possible. However you can use a variety of different cards in the UX in the meantime to show warning messages based on a predetermined criteria. KPI or Field cards would be especially effective in showing written messages while you could also use picture cards to display visual alerts if certain formula driven conditions are met.

ChrisHeathcote

@DMManalili It is not possible to format the grid in the way you current want as you are trying to combine non time series data which contains properties of the list item with time series data which is the final calculation over time. Description does not require the time dimension but you are trying to combine them. This is a common request when you are asked to do a straight copy from an Excel worksheet. Lets remember Anaplan is not Excel. The solution here is to display the data in two grids. Separate out the description line item into a new module without the time dimension as this is not a function of time Retain the time series module and the line items that require time On a board both grids will synchronise and the data will update accordingly when the user selects the desired list item I would recommend that the description is place at the top of the board with the line item as the row and the list as a selector. The time series data could be presented as you have it and when the list item is selected the description sitting above will change to show details of that line item. Chris

ChrisHeathcote

The best approach here would be to use a list. Create a list using 1 - 100 with a property formatted as number from 1 - 100. Format your input with the list and create a additional line item formatted as number. Reference the list property so that you can convert the list selection to a number format to use in down stream calculations. This would be the easiest and simplest approach. However, you will not be able to set a default and will have to use one of the other methods if this is still required. Thanks, Chris

ChrisHeathcote

@tompatrickting Have you explored using a line item subset to turn the line items in your system module into a list. You can then assign this to your pick list line item. However, without further details regarding what you are trying to achieve it is difficult to elaborate.

ChrisHeathcote

The first suggestion would be to rationalise your metadata and standardise it. Do not allow different names. Change is a process but teams will adapt. A new planning model if significant should be accompanied by a detailed and widespread change management project to ensure that these issues are dealt with and that chances of successful adoption is maximised. What you are suggesting would cause significant data integrity issues as there would be a lack of consistency across the organisation and would inevitably cause confusion. Therefore, I believe it is not possible within Anaplan to allow list items to possess multiple names for these very reasons.

ChrisHeathcote

@NishaS From your brief description it would seem that you are not filtering the view of the import data prior to the processing the import action. The use of the page selector is not the same as a filter. You are simply limiting the view of the data based on the selection. The other time periods still exist in the view but they are simply not visible. To target your import you need to filter the view of the source data to only show the time periods that you want to update. It would appear that you are trying to target specific years for import. I will proceed on this assumption. Create a module containing no dimensions called, 'Year selector.' Create a line item called, 'Year.' Format this as time period year Create a module dimensioned by time only. Create a line item called, 'Year.' Format this as time period year Formula PARENT(ITEM(TIME)) Create a line item called, 'Year Filter.' Formula Year=Year Selector.Year In the module that you are import ( the source data ) use the, 'Year filter,' to filter your data by the required year. Save as a view Publish the line item from the 'Year Selector,' module to a dashboard and use this to select the required year for import.

ChrisHeathcote

@johan.marketoft From your post I think you are trying to project the employee properties into future periods. If this is so then you can achieve this by using the follow approach. Create an employee properties module dimensioned only by the people list Create a line item to hold the FTE, start date, start period, end date and end period Format you date line items as date, the period line items as time period month and the FTE as number Start period formula =period(start date) End period formula =period(end date) FTE, Start date and End date will be populate manually via an import or by a user Create your reporting module dimensioned by people and time period month Create line item FTE and Active? Format FTE as number and Active? as boolean Active? formula =ITEM(TIME)<=Employee Propeties.End period AND ITEM(TIME)<=Employee Propeties. Start period FTE formula =IF Active? Then Employee Properties.FTE else 0 Where the time period is between the start and end period within the properties module the FTE value will flow through into the target module despite what the current period is in the model time settings. Chris

ChrisHeathcote

You may wish to highlight the parent or total of a list when displaying data on a board or worksheet. Conditional formatting uses line items to set the criteria for the conditional formatting and it is not possible to specifically highlight a summary or parent list item directly. However, the following steps can be taken to achieve this. For the list in question ensure that you have created a properties module. Create a new line item and format as a Boolean. Set the formula = TRUE Create a new line item in the target module. Set the formula = IF Property module.boolean = TRUE THEN 0 ELSE Change the summary settings for the line item to formula. All parent list items for that list will now be set to 1 while all the children remain 0 In the UX pivot the line items to either the column or row, select and update the conditional formatting settings using the line item above to qualify the criteria. This is a very simple solution which will allow you to highlight any parent of a list and can be repeated over any number of dimensions if you module requires it. Chris

ChrisHeathcote

@x4uhaj Why is it important that the names are retained in the model? You could allow users to update the names but store the original name within a list property. This would allow you to reconcile back to the original name if required. However, this would require all list items to have a unique code which must remain unchanged.

ChrisHeathcote

What you are requesting is not possible as all the modelling data is held in the underlying model. The UX is simply a tool to display this data. Sorry

ChrisHeathcote

Hi All, I am working through designing the model schema for Level 3. However, I can not find any good visual examples of how they could look. What should I include in the design? What is the most effective way to include dimensions and should key calculations be shown to illustrate how the data is flowing from one module to the next. Would welcome any examples of model schemas that people feel are good examples of best practice in this area. Thanks, Chris

ChrisHeathcote

@tompatrickting To synch the filter to the time selection you need to base the function on that line item. From the screen shot I assume you have published a line item format to time period month. Instead of referencing PERIOD(CURRENTPERIODEND()) just reference that line item. When you select from the drop down the filter should automatically update.

Online Status	Offline
Date Last Visited	yesterday