About hgrosen

Suggest to add ability in Cloudworks to create custom load calendars. Not all data integration loads follow a recurring pattern but are instead based on custom load dates. Adding ability to e.g. specify a specific load calendar for the next 12-18 months will ensure load dates are aligned with business processes and reduce the need for triggering loads manually or through other task management solutions. As an example, some core processes may take place on the second Wednesday of a month while load then needs to take place the following Thursday and Friday. I.e. the first load should not always be on the second Thursday of a month but rather the first Thursday following the second Wednesday of a month. At the same time, some dates may need to be placed sooner or later due to various national holidays. Timing of the load dates is decided for at least the coming 12 months and could therefore be maintained in a custom load calendar up front instead of manually triggering the loads whenever they deviate from a recurring pattern that is covered by the normal trigger frequency settings. 。。。View more

将非常有利于模型构建器see the calculation time (e.g. from model open) of the individual line items with formulas. The current cell count is a great help when it comes to optimizing the model and identifying how to reduce the size hereof. However, the calculation time of the different line items is also a very important factor when it comes to ensuring the model can be opened fast and that the model in general performs well. Ideally, this should be shown in the modules right next to the cell count and in the line item overview to help identify the most performance-heavy calculations. 。。。View more

Suggest to show the general process progress in the new UX. In the classic UX, it is possible to see which specific action in the process chain is currently being processed. The new UX only shows the progress bar per process step but without any information at all about which step is currently being processed and it is therefore impossible for the end user to see if the process chain is almost done or still in the early phase. When the process is finalized, small tick marks or exclamation marks are shown next to the process steps, but would be helpful if these are displayed as every process step is completed (see example I created below). This way the end user or model builder can still have the steps collapsed if not interested in the details, but can also expand and see the general progress of the process. Ideally, there should be both a progress bar for the full process and for the individual process steps. 。。。View more

Suggest to enhance the current import error report in the new UX. The new overview only contains very limited information about any errors which occurred during import and it is not possible to get a preview of the errors as you can in the classic UX. At the same time, the ability to export errors is limited to 50,000 rows and for the full process chain. I.e. if a process consists of multiple actions it would not be possible to see or download the full error log for the process - only for the first action(s) until the row limit has been reached. Some improvements which would help transition from the classic to the new UX: Ability to see preview of individual process step errors after import (as in classic UX) Ability to export individual process step errors (as in classic UX) Show least occurring errors first (would ensure the 50,000 row limit would not be an issue) Ability to hide selected types of "errors" (e.g. the "Another row has already been processed with this key" error is not really an error and confuses the end user) 。。。View more

如果Anaplan提供了进口数据的更多详细信息，将非常有益。除了正常错误日志外，如果例如最大/分钟值，异常值，异常，趋势，大多数/最不常见的项目，尺寸项数等可以显示导入时，以帮助用户快速地检查数据导入或帮助早期识别有趣的数据观察结果。这可能有助于减少在数据中心或辐条模型中构建自定义数据验证步骤的需求。 。。。View more

建议与SAP解决方案建立本地集成。许多Anaplan客户都使用SAP解决方案，例如SAP ECC，S/4 HANA，SAP BW等，并且在很大程度上取决于大量来回流入Anaplan的数据。与这些解决方案集成通常需要额外的层，例如AWS或类似的层，然后再次使用API​​将其连接到Anaplan。设置此数据流程可能很麻烦且难以使用，而其他解决方案和平台则提供内置功能，可以直接利用SAP查询，表，层次结构等。添加此功能将帮助客户利用和加快数据集成，因此将其加快速度。显着提高了Anaplan的可用性和用例。 。。。View more

Suggest to add ability for model builder to change the default setting for list subsets. I.e. add option to select whether a subset setting should be true or false for any new list items added. This will make it easier and more flexible to work with subsets, and help avoid having to create a dummy module and action to import the subset setting after adding a list item. 。。。View more

Is it correct that the process error log in NUX is not able to display the complete list of errors detected? I tried running a big process (57 actions incl. 6 flat file imports) in the NUX which works fine in the old UX. The process also completes correctly and with the right result, but I cannot seem to open or save the complete error log as I can in the old UX. E.g. it looks like the error log I can save only includes the first import error observed and with 50,000 rows, but everything else is missing. Also, I find it more difficult to see the progress as the status does not mention which action is currently being processed as in the old UX - any way to display this? Alternatively, we will have to look into the progress bar module mentioned in another thread. /Henrik 。。。View more

添加能够在Excel加载项中的表中同步过滤器的能力。使用Excel加载项并从不同模块中提取数据，不同提取物的某些过滤器重叠。这里的一个很好的例子是预测周期或特定版本。目前，我们必须更改每个表中的预测周期，以便将最新的数据和同步数据输出。如果我们可以为具有多个Anaplan模块的Excel工作簿选择“全局过滤器”，那将变得更容易 - 类似于您在例如MS Office的SAP分析。 。。。View more

建议将“开源模块”能力添加到Nux，含。旧UX中可用的当前分析选项。现在，我们的用户可以在旧UX中使用开源模块功能，只要他们想挖掘详细信息，查看所有基础公式/注释，并进行临时分析。特别是，比较函数非常重要，因为这使他们能够快速做到，例如周期开发周期的临时比较，而无需仪表板中的专用比较表/图。当然可以在仪表板上构建比较表/图表，但是仅在临时进行一些分析。同时，拥有此功能作为最终用户还提供了一个临时解决方案，直到准备好模型构建器为仪表板添加标准分析元素为止。 。。。View more

建议添加配方奶钻至NUX。使用NUX时，没有配方钻的选项。这是我们用户的关键功能，因为他们需要查看在进行根本原因分析时如何计算数字。同时，应像今天在旧的UX中一样显示进入公式的特定值。您可以将NUX中的链接添加到基础数据/模块中，但是在使用例如。在应用偏移或依赖大数据输入表的情况下，当最终用户不仅显示公式，而且还应用的确切值时，最终用户要容易得多。与Excel和其他竞争工具相比，这是旧Anaplan UX的当前优势之一，使我们的用户非常容易挖掘数据。 。。。View more

When copy/pasting values from an Excel table to Anaplan, it only includes the decimals shown in Excel. E.g. if the value 0.5499 is in Excel but the cell in Excel is set to only show one decimal place, the value displayed will be 0.5. When copy/pasting to Anaplan, 0.5 will be used and not the full 0.5499. This issue can of course be avoided by either uploading the file to Anaplan or by extending the number of decimals shown in Excel before copying. However, when not all linked models exist within Anaplan (yet) and when some of the input applied from Excel is not always positioned in the same exact cell, this becomes an annoying extra step to keep in mind for the end user and increases the chance of our models showing the wrong result. Suggest to change this for both the old and the New UX so copy/paste from Excel includes all decimals, even if not displayed by default. 。。。View more