About dameyer01

dameyer01 · ‎09-28-2021

@Sagar123 Here is the Anaplan technical documentation for the Round function. ROUND - Anaplan Technical Documentation If you're trying to round your Default Forecast line item, best practice would be to calculate the Default Forecast = 'Baseline Forecast' * 'Growth rate %', then have an additional line item like 'Rounded Default Forecast' = ROUND(Default Forecast). You can add the additional arguments to the Round function as necessary according to the technical documentation.

dameyer01 · ‎09-24-2021

@michael.chefer To use the Delete from List using Selection action, the referenced Boolean must be in a module dimensionalized by only that one list (and line items, of course). Is it necessary for your module to have the two lists in the dimensions? If yes, you'd need to create a staging module that's flattened to the one list which references your current module.

dameyer01 · ‎09-21-2021

Any updates on this idea? Seems like there was a healthy amount of support, and would definitely help instill better habits in model builders.

dameyer01 · ‎09-21-2021

Not sure if you're still facing this issue, but Quick Filter shouldn't cause issues with Synchronize Selection, only attempting to Hide or Show list members. In fact, the error message you screenshotted calls out "Hide" and "Show" as unavailable, and not the Quick Filter option.

dameyer01 · ‎09-02-2021

@kjochim When you edit the view in the card editor, click one of the row/column labels whose order you want to change. Then you can click the 'Totals Position' icon to change the ordering of the hierarchy. Note: this button is only available from the Custom Views. Alternatively, you can create a saved view of the module from the model building environment with the Totals Position set in the saved view. Then you can select this view in the UX card builder under Module Views.

dameyer01 · ‎01-19-2021

@rob_marshall Big + fast >> Small + slow

dameyer01 · ‎01-19-2021

在之前的帖子,我想问你如果有一个方法se the FINDITEM function to determine if a list item is a member of a subset. The answer at the time was no, but you could create a line item with an Applies To on the subset, and set the formula to TRUE, then you could create another line item with Applies To on the full list and reference the subset line item. Turns out, you can use FINDITEM on a subset, but you have to type out the subset name, as opposed to navigating to the list and clicking the subset header. This was demonstrated in the line item subset training, which I validated in my L1MB model. This might be common knowledge, but I wanted to put it out there, in case there are any out there that were like me thinking, "There's got to be a better way!"

dameyer01 · ‎01-13-2021

I do! Send me a DM and I can send your way.

dameyer01 · ‎12-03-2020

@JosephA You may need to re-visit the format of your time import on the Time tab of the import mapping screen.

dameyer01 · ‎11-25-2020

@neg177 Can you provide the line item labels on the rows and the formula in question? I can't tell which rows are relevant or what rows you're referencing beyond the highlighted one.

dameyer01 · ‎11-25-2020

@Kunal0489 I believe the 'WWYY' format expects only a numeric input. So, your "Week 11 FY19" entry would be "1119". Below is a Best Practice page on handling time imports. Untangling Anaplan Time Mapping in Imports

dameyer01 · ‎11-23-2020

@tejaswini I recommend creating a separate module with no dimensions with a 'Approve All Profit Centers?' Boolean, then add a 'Final Approval' line item in the original module. Then your 'Final Approval' line item's formula would be: 'New Module'.'Approve All Profit Centers?' OR 'Approve'? It could then look something like the below.

dameyer01 · ‎11-23-2020

@kotoponus My guess as to the intentions is just to demonstrate different ways to populate those Booleans. Again, working from memory, but I think the Location Details module in the Supply Chain model is formula driven based on what's in the subset, so I think it's more important to have the subset populated for now, whether directly from the CSV file or imported via saved view as described by @ashish.banka.

dameyer01 · ‎11-20-2020

When you set up the import from the Excel file, set Time as Column Headers and Line Items as Column 1. Then on the tabs, you can specify the date format and maps the row labels to line items appropriately.

dameyer01 · ‎11-20-2020

I'm not totally clear on the goal, but would it work to create a 'Securitization - Baseline' module that doesn't have any formulas that you could then upload your Excel file to? This would retain all the data elements in your Excel file and allow you to reference it.

dameyer01 · ‎11-20-2020

The 'Distribution Center?' Boolean in the Location list is actually a subset, which can't be referenced from a module's line item. It doesn't hurt to populate the line item from your flat file, but if I remember correctly, it won't end up driving anything through the rest of the build, so either way should be fine.

dameyer01 · ‎11-19-2020

@rob_marshall - Sorry, but I can't figure out how to send you a DM. When I click the envelope icon on the top-right, I get a "Sorry, this content no longer exists" page. Is there a different link I should use?

dameyer01 · ‎11-16-2020

@rob_marshall I might not have explained the situation correctly. The 'IVAM', 'DIAM', and 'CCAM' columns in the account assignment table are line items (list-formatted by the Account Managers list). Position type is being maintained as a property of each account manager position in a module. If I create a module dimensionalized by Position Type, how do I reference the position type of each account manager in the SUM statement?

dameyer01 · ‎11-16-2020

I have a list of accounts and a list of account managers, broken into three categories (IVAM, DIAM, CCAM). Sales managers must assign an account manager from each category to every account. I want to aggregate the account metrics for all the accounts managers in a single table. The first image below shows the account assignment module, the second is the aggregation table. Currently, my solution is something like: Total 3yr Avg OIT: IF AM Type = AM Type.CCAM THEN 'Account Assignments'.'3yr Avg OIT'[SUM: 'Account Assignments'.CCAM] ELSE IF AM Type = AM Type.IVAM THEN 'Account Assignments'.'3yr Avg OIT'[SUM: 'Account Assignments'.IVAM] ELSE IF AM Type = AM Type.DIAM THEN 'Account Assignments'.'3yr Avg OIT'[SUM: 'Account Assignments'.DIAM] This solution works, but is a very brute force formula and inelegant. Any ideas on how to improve this? If we end up expanding account manager categories or metrics, this solution does not scale well.

dameyer01 · ‎11-16-2020

1) Does Module 2 need to accommodate other profit centers besides P9999? If not, you could create a list subset whose only member is P9999, then dimensionalize module 2 by that subset. 2) In Module 2, you could create a staging line item that pulled data from Module 1. Then you would have another line item that would have the condition that IF ITEM(Profit Center) = Profit Center.'P9999' THEN Staging Line Item ELSE [insert else statement here]. If there are many line items, this might not be easily scalable, but the result could look like the following:

dameyer01 · ‎11-10-2020

1 - After you create the "Display Name" property on the Properties tab within the Employees list, go to the General Lists screen. There you can designate the Employees list as a Numbered list and select "Display Name" from the dropdown in the Display Name Properties column. 2 - Was there a question with this one?

dameyer01 · ‎11-10-2020

Glad you were able to find a solution that works for you! I have two additional thoughts on your conclusion. 1) You should be able to put the 'Payment frequency = Payment frequency.Yearly' clause in front of the IF statements, so it's not being evaluated every time. So it would look like this: Payment frequency = Payment frequency.Yearly AND IF Payment # - 1 = 12 THEN TRUE ELSE IF Payment # - 1..... 2) Although your formula does what you need it to, it could be shortened so that the period in question is being evaluated against the period in the 'Payment 1st month by item' line item. 'Next Payments ?': Payment frequency = Payment frequency.Yearly AND MONTH('Payment 1st month by item') = MONTH(PERIOD(START())) AND PERIOD(START()) > 'Payment 1st month by item' That said, it matters most that your solution works, which it clearly does!

dameyer01 · ‎11-09-2020

此外,如果能取消勾选enu Option also removed that item from the pop-up when a user right-clicks a column header. Currently, they still appear, but are grayed out (first image). It would be cleaner to have it removed altogether, similar to the carat dropdown at the top-left of the table (second image).

dameyer01 · ‎11-09-2020

Could something like this work: MONTH('Payment 1st month by item') = MONTH(PERIOD(START())) Then you're comparing the model month with the month set in your line item, regardless of the year. If you wanted to just flag the future payment period, you could add: AND PERIOD(START()) <> 'Payment 1st month by item'

dameyer01 · ‎11-09-2020

In Blueprint Mode, you would change the 'Summary' value to 'None' for the relevant line items.

dameyer01 · ‎11-03-2020

As your importing the file, in the import mapping window on the Line Items mapping tab, you can click 'Edit' on the right side of the window to set what date format to expect in the upload file.

dameyer01 · ‎11-02-2020

What does your Employee.Region formula look like? I think I was able to achieve your goal using Firstnonblank. Accounts module (I combined the two accounts modules in your schema for simplicity) - 'Employee' and 'Region' are both list-formatted Employee module - 'Region' is list-formatted

dameyer01 · ‎11-02-2020

I believe 'Category: Demand Modules' is just the instruction to put your DEM01 and DEM02 under the '-- DEMAND MODULES --' dummy module to keep your list of modules organized. This should mirror how your SYS modules are under '-- SYSTEM MODULES --' and DAT modules are under '-- DATA MODULES --' There is no functional impact to the model, only helping to instill best practices in model organization.

dameyer01 · ‎10-13-2020

During our Territory Assignment exercise, the type of account dictates whether a particular rep type can be assigned to the account. We facilitate this via DCA. However, because the account types are sometimes in flux during the assignment process, a rep could be assigned to an account that they would later be ineligible for. While DCA would hide this assignment from the user's view/export, Anaplan still sees the entry when referenced by another line item/module (screenshots attached). This can lead to misleading summaries when summing up a territory's total number of accounts, historical order volume, etc.

dameyer01 · ‎10-02-2020

In our ICM model, we have a quota acknowledgment process that "stamps" the displayed quota value and the "acknowledged date" (which the user enters manually) via an import action. As the model builder, I would like to leverage some kind of DCA on the action/process that would disable the button unless certain criteria are met, in this case, ISNOTBLANK(Acknowledged Date).