About bdeaton

What are your applies to and formatting settings for each of the following? Source line item Target line item Two mapping line items used 。。。View more

I don't really know anything about C#, so I can't really help there. From an Anaplan perspective, I would try the following: Test the file creation & action Run the steps that create the csv file Make sure the import action you created in Anaplan is published to a dashboard Press the button, navigate to the file created above (you shouldn't be prompted for any additional information other than file location), and attempt to load. See if any errors are produced. Assuming all steps in step 1 work, then I'd check the following: Name of the file being produced via the C# process vs the name of the file used to originally create the action. We use Anaplan Connect and sometimes a mismatch here causes issues. You can check the name of the file on the imports screen. If the file names match exactly, and the action runs manually without issue, then it seems likely it's a C# issue and not an issue with Anaplan. I'm not sure where to go from there but perhaps someone else here will be able to chime in with additional information. 。。。View more

因此，您编写的C＃查询创建一个.csv文件，然后您将该文件手动加载到Anaplan中？还是C＃查询有两个步骤：创建文件然后加载文件？ 。。。View more

Specifically, there are couple things I'd point out to you about the formula you used: After the comma, it appears you typed in "SYS08 Employee Details'.Role" in an attempt to also have the LOOKUP statement apply to it. You have to actually repeat the LOOKUP for each item you want to lookup. Second, it kind of looks like you typed in the module name since the single-quote at the beginning was left off. Names of modules/line items/etc... will require single quotes around them if they contain special characters or numbers. As a general rule, I will usually always include quotes if I am typing in a module name manually. If I use the "point and click" functionality, Anaplan will apply single-quotes when needed automatically so you don't have to worry about it. In either case above, you should get a syntax error when trying to submit the formula. Make sure you look (and share, if you need to ask for assistance) at what the error message says as it can help narrow down what the issue is. 。。。View more

不，红色并不一定意味着它是错误的。每个维度都会得到不同的颜色编码。我将检查“订单”选项卡（第三个）。您可以提供外观的屏幕截图吗？这是从文件还是从另一个模块导入？而且，如果您从Anaplan（不是通过C＃）运行它，您是否会收到任何错误？如果是这样，您会遇到什么错误，您可以提供屏幕截图吗？ 。。。View more

For the import action you are trying to run, is it importing from a file to a module or from another module/saved view to a module? Are you able to run the action directly from the Anaplan interface (i.e. try to publish it to a dashboard and press the button) without issue? 。。。View more

We recently had a new model builder ask about this task. I think it is not set up in a very clear way. You cannot have dimensions that are part of the module that are not part of the saved view. I told our model builder to just leave the dimensions set at their defaults for that first saved view and add the filter as requested. 。。。View more

If you have access to the Hypercare service, this information is available. But I think this information should be more widely available and I think the Tenant admin would be a great place for it. 。。。View more

I'm aware that dimensions can't be added/removed from a saved view. As I recall it, the instructions had something like the following specified: Pages: N/A Rows: N/A Columns: N/A Filter: XYZ Filter But the module has dimensions. If the module has dimensions, it is impossible for pages, rows, and columns to all be empty of dimensions. That was the confusing part. I instructed the user of how saved views work and to just move on. But it would be preferable to clean up areas of confusion in the training courses. 。。。View more

这对我们来说也是一个问题。我们已经设置了一个必须执行以下操作的过程：1）我们将在仪表板上按下一个按钮，该按钮会提示我们获取该文件失败（但它将存储文件）3）然后，我们将转到用户列表并按“导入”按钮，它将从我不特别喜欢此过程的存储文件中导入，但是它可以使用。听起来您的可能是相似的。我们最终将其完全更改，现在正在模块中设置用户访问，然后从该模块导入到用户列表中。我们不会遇到任何问题。我想您可以将其设置为从.CSV文件导入到模块中，然后以一个进程作为临时解决方法的用户列表。 。。。View more

We are currently on Anaplan Connect v1.3. Our IT partners have been working since before the beginning of the year on trying to convert to v1.4. We are currently in a holding pattern awaiting v1.4.2 as v.1.4.1 cannot handle UTF-16LE files. We are therefore completely unable to move off of v1.3 until this is resolved. Is there any update on when v1.4.2 will be available? 。。。View more

您可以使用IF / THEN &项目(剖面)语句your formula to drive different calculations based on PROFILE. This would allow you to use the dimensions already in your module. If you are wanting to create some sort of input process for the PROFILE instead of having all PROFILEs be calculated simultaneously, then I would ask: Do you want the user-selected PROFILE to change the calculation for all users or just change the view for that individual user? If it is a global setting, the I’d say that instead of dimensioning the module by PROFILE, create an input line item (no dimensions, separate module) which is list-formatted as the profile list. Publish that line item to the dashboard along with the calc module. Then, the calc module could do LOOKUP type formulas based on the user input. We do this kind of set up frequently with time - modules display one time period based on a user input. If you are wanting the choice to be user-specific, then you can do basically the same as above, but add users as a dimension of the input line item and the calc module. This will allow each user to input a PROFILE and see the results but it won’t affect what other users see. 。。。View more

A few questions: Can you include some screenshots or examples with data so it's easier to see what you are trying to do? Do you want a sum of prior 8 months at just a single point in time or do you want to calculate that for every month (i.e. January 19 is the sum of prior 8 months data, February 19 is the sum of a different 8 months, etc...) Does your final target need to be dimensioned by time? A few options come to mind, depending on the above questions/answers: Use TIMESUM - you wouldn't need a boolean line item with the last 8 months checked, but instead would specify that you want to add up the prior 8 months and it would do that calculation for each month in your target line item. https://help.anaplan.com/anapedia/Content/Calculation_Functions/All/TIMESUM.html Add up multiple LAG formulas - similar to above, but longer formula. The LAG formula is a bit easier to use than TIMESUM. https://help.anaplan.com/anapedia/Content/Calculation_Functions/All/LAG.html Set up a new staging line item that is dimensioned by the same thing as your original amount. In this staging line item, use an IF/THEN statement to say IF Boolean checked then Amount else 0. Then your final line item would be dimensioned by everything that the original amount line item is except for time. If you set your final line item equal to the staging line item, it will add up across time. Happy to share more detail on the above, depending on what exactly you are trying to do. 。。。View more

我们已经想了很多关于测试/ past year. We ran into some difficulties with our last new model in that the testing methods we had established were overly cumbersome in some ways that didn’t add a lot of value as far as mitigating model risk. We spent some time putting together a framework that is meant to provide our model builder with guidance on selecting appropriate testing methods. We are trying to emphasize that various methods are acceptable and professional judgment should be employed to ensure that testing is completed which will help us to appropriately mitigate model risk. Testing is always required and model builders must document their testing, but we try not to dictate that one specific method must be used in every case. The idea is that security updates are very different from small dashboard tweaks which are very different from creating new journal entry processes, so the testing should be different as well. We view it as the model builder should be taking some steps to feel comfortable that the build is correct, so they should be able to put together a test script that documents their process to get to a level of comfort and another model builder ought to be able to look at the test script and feel comfortable with it as well. For live models, we also require a change log to be maintained. This is an Excel file where the model builder must list out all of the changes that were made. They should specify the item that was changed, provide a brief description, include the old/new formulas (if applicable), and answer a few key questions that are designed to help them think through downstream impacts of the changes (regarding security updates, impacts to existing data, & new maintenance requirements). Once an item is complete, the model builder would also provide a link to the testing documentation and then the change log and testing documentation would be reviewed by another model builder prior to promoting changes to production. We are also trying to tie testing directly to user stories. We strongly encourage/require that every user story be tested and testing documentation be prepared. Again, allowing the model builder to use professional judgment as far as what testing is necessary. If we find that we need to go and edit a previously-built item, then that might become a new user story created during the sprint. Or we might include certain re-testing elements as a part of a future test script. On top of testing each user story/change log item, we also encourage the model builder team to consider what other tests would be appropriate for the development being done – that may include parallel testing, regression testing, usability testing, and/or security testing and is very dependent on the specific development being done. Our COE team stays very involved in testing at this point. I would say that about 50-75% of all model changes are either done by or reviewed by the COE. We are trying to reduce that number and put it more in the hands of the model builders, but we do want to make sure that sufficient and thorough review is done, especially for changes that are more high-risk and many of our model builders are still fairly new to the tool. We also primarily manage the change logs and ensure changes are appropriate documented, reviews are lined up, and summaries of changes are provided to the model owners to request model promotion approvals. One thing we are still trying to fully solve is how to get to a good level of comfort that all changes to existing models are included in the change log (and thus tested). I would love to hear others’ thoughts on this. Do other admins review the ALM comparison reports back to the list of expected changes or do regular model compares to check this? How detailed are your checks? Does anyone else do something like a change log where all the model changes are documented/reviewed? 。。。View more

Your name – Brittany Deaton Your company - Unum Where you are on your CoE journey – We are still a fairly new COE but have been building models at Unum since 2017. Although we weren’t officially a COE until 4Q18, our models to-date have been limited to within the GFP&A group, so we self-managed and have continued some of the same trends we established during the first two years into our official COE. If your COE already exists, how long has it been around, and what is your role – we established the COE officially in 4Q18. I am currently a Director, Actuary and leading the COE team. What you hope to get out of this COE section of Community (we constantly monitor this and are always looking for ways to improve!) – I would love to have opportunities to hear and share ideas and best practices, especially around model governance. One of my goals for our COE initially is to make sure we make a solid transition into a place of stability (building models is no longer a new thing to Unum so we should be working to achieve a maintainable pace and build a solid governance structure). 。。。View more

@davidsmith-在摘要表中，您确实注意到导入时间与尺寸模块相比平台的时间较慢。我认为这意味着我们仍然相信使用“ 2D”表进口的速度更快，正确吗？您是否知道导入到文本形式的订单项与列表格式的订单项有任何导入正时差异吗？ 。。。View more

当将数据/属性加载为列表属性时，您上面列出的尺寸（基于格式的字节数）还是相同的？ 。。。View more

@RyanMonique I've been using the add-in all day today. It's awesome! 。。。View more

@DavidSmith我倾向于同意佛rmulas should often be broken up if they are complex, but this is sometimes a battle against size issues in some models and longer/complex formulas is sometimes (but not always) the best option to limit space requirements. Looking at our models, we probably should simplify in a lot of cases. But, as with almost anything, there are trade-offs to be considered. Even simple IF/THEN formulas can benefit from the spacing that this add-in provides, however. So I still think it does have value. And for formulas that are already written and need to be simplified, I could see where this add-in might help to more easily identify the different pieces that could be pulled into separate line items to get back to a place where formulas are simpler. 。。。View more