About Guido.kaandorp

This will speed up API development and runtime both. The API requires ID's as parameter, however Anaplan UI shows only the Name. When using API for sending data to Anaplan or triggering a process we now use the name for searching the id. Currently this requires additional looping in our API framework. If we know from the Anaplan UI e.g. the processId upfront we can directly implement it with this ID rather then looping over all processes till the API found the correct Id. ... 查看更多

限制数字格式将很方便。这将节省其他验证检查/可视化。例如： - 数字必须为正 - 数字应该是一个整数 - 数字应在0-10的范围内，这就像一个因下拉列表，但是现在限制了格式的输入的数字。 ... 查看更多

如果将具有多个维度的模块显示为行和/或列，并且在同一页面/仪表板上显示更多详细信息，那么如果系统通过单击单元格进行同步，将会很棒。这是最终用户的直观行为。例如：1月21日2月21日3月21日客户A产品1产品2 15客户B产品1 20产品2产品3 12当点击15时，另一个模块将在2月21日同步，客户A和产品2自动提供更多见解。在当前设置中，您需要单击所有3个单独的标题以达到相同的标题。 ... 查看更多

When we are creating new data feeds to Anaplan via API, it will set the new file on private as default, which you can't change afterwards anymore. In our case the file would be created by our 'AnaplanCoE' user we are using for the API. It would be great if you can change the file that it will be the default for everyone or as least all admins. In this case we can develop and testing the processing of the source files with our own logins rather then the generic AnaplanCoE user. We have 2 work-arounds: 1. test/develop the new import actions using the AnaplanCoE user (however we would only like to use this for the API's) 2. Manually adding the new file ones and set it for Admins/All. However this requires a sample data file offline for manual upload, with the risk that the structure could be out of sync comparing with the automated one by API. ... 查看更多

Just want to share this in the Benelux user group: https://info.anaplan.com/2020_Q4_01_EMEA_Benelux_Event_SpotlightonConnectedPlanning-Benelux_01-LandingPage.html ... 查看更多

在模型设置 - >源模型中，您可以编辑映射并将源更改为例如生产模型而不是开发模型。对于我们的某些模型，我们已经重新创建了多个开发模型（生产副本），这导致源模型列出了许多非现有模型：模型A〜1模型A〜2 Model A〜2 Model A〜3模型A〜4然后，所有这些模型都被“映射到“正确”模型A'。如果您可以更新默认源模型，那将是很好的，从而导致多个原始源模型合并为一个单个源模型。这将使概述更加精简，并降低遗漏重新映射的风险。 ... 查看更多

当前的条件格式是基于线ems, in addition to this we like to have such possible for list items as well. E.g. highlight particular products, customers or months. Conditional formatting on line items should still be possible in addition and if for a cell both formatting (based on list item and line item) would be applicable, then you should be able to choose what is the master. In current conditional formatting set-up, Conditional formatting on list items is not easily possible. The only workaround would be implementing conditional formatting to each line item based on another line item. However this workaround will cause that you can't use additional conditional formatting on line items. ... 查看更多

主数据列表通常需要在数据中心和辐条模型之间同步。目前，我们按以下方式执行此操作（对于增量负载）：在辐条模型中：1。将所有列表项目的属性设置为false 2. 2.从数据集线器中的数据中加载到sapk Model（inclage）。“使用”属性的真实标志）。3.删除所有不使用“使用”的项目，对于删除未使用的项目，还有更多的口味。这只是一个例子，但是它总是需要3个步骤。在模型之间拥有一个天然（子）列表同步功能，这是很好的。这将节省大量型号的构建时间，从而产生更精简的型号，​​因为它每次都需要1步代替3步，并且可能会减少容易发生的错误。通过一个Singe Action，您可以根据其代码同步2列表。 ... 查看更多

It would be nice to be able sending custom return codes/messages to the API / Anaplan Connect. This will help us in be more proactively in case of errors. Think about a validation dashboard, which check data consistency. It could be that after a new data feed some functional data errors are flagged up at this dashboard (e.g. missing mappings). In stead of going into the dashboard manually, it would be nice that if an error occurs we are warned directly via an API failure. As a current work around we are importing an error text into a list formatted line item. As this gives a technical failure of that import action it can be grepped by the Anaplan Connect script and a mail is send to our Anaplan CoE team. ... 查看更多

As model builder I would like to make use of sequential lists (Array or Linked list) to avoid circular references. This can be useful in many calculations.. Native functions like PREVIOUS() or NEXT() could only be applied on line items which are on the time dimension. Such functions should then also work for the sequential list as well, without causing a circular reference. Theoretically you don't have a circular reference if the list is properly sequenced with a PREVIOUS and NEXT item. Sequential lists you could think about: Monday, Tuesday, Wednesday, .... Jan, Feb, Mar, .... Asset nbr 1, Asset nbr 2, Asset nbr 3, ... (we have modeled whole manufacturing routes) Workaround: At the moment if I require this I map the original list item to a date. Do the calculations on that 'date' item and then map it back to the original list item. E.g. for an allocation algorithm allocating demand based on margin using constrained capacity buckets. The workaround is however limited as you can only use 1 time dimension per module/line item. ... 查看更多

嗨，作为模型构建器，开始使用@JoeyMorisette Time Time Timy Timy Time的命名惯例将非常方便。通过一些命名转换，在名称上对模块/操作（或理论上的任何对象）进行排序也很容易，但是，如果您将模块发布到仪表板上，则不想看到名称out01xxx，out02xxx等...对于最终用户。我的想法是添加一个显示名称（功能名称）列，如果填充它，该列将用作显示名称。否则，它将显示原始（技术名称）。这将帮助我们建立更好的模型结构。 ... 查看更多

我希望能够从Anaplan触发API（例如仪表板上的按钮）。这将使将数据发送到另一个Anaplan模型或基于最终用户的其他系统事件，而不是在Anaplan之外安排该数据。最终，它将与第三方解决方案（高级分析算法，Phyton脚本等）更好地集成，并可以将Anaplan用作最终用户前端。 ... 查看更多

示例：我们有一个基于维度A和数月的模型，并包含2个行项目：-line项目1（手动输入）：仅适用于尺寸A -Line项目2（具有公式）：适用于尺寸A和几个月如果我们将此模块发布到以一个月为页面选择器的仪表板上，则不可能更改行项目1的值1。但是，无论选择哪个月，您都应该能够修改该值又一个月的值保持不变）。当前（丑陋的）解决方法是彼此发布2个模块。在右侧，一个带有行项目1的模块中的一个，没有一个月的维度，一个在左侧，一个在一个月度的模块上，左上有项目2。这个理论示例偶尔发生在模型构建时。 ... 查看更多

Periodically we are making an overview of all our models and their size. This is a manual exercise and only possible to collect via 'manage models' in each separate workspace. We then copy the model sizes every month in one of our models to monitor growth. It would be nice to be able to see the model size via the Anaplan Administration. And even better to see the model size over time. This will save manual work. ... 查看更多

To clean up old line items it is handy to now it hasn't be published to any of the dashboards. ... 查看更多

We have some instances where we are incorporating multiple actions into more processes. Instead of adding action A,B,C,D,E,F into 4 different processes, we could bundle this into Process X. Process X can then be used in the 4 different processes. This will make the maintenance more convenient. E.g. we can ad action G or remove action C at ones and assure the sub-process are always in sync within the multiple processes. In our data hub we have this with >30 actions which are all incorporated into 3 different processes. We had occurrences in the past that changes were not incorporated in all of 3 which cause incidents. ... 查看更多

https://community.anaplan.com/t5/idea-exchange/alm-data-refresh-development-model-with-data-data-data-of-the-production/idi-p/45984#m2751 ... 查看更多

在大多数模型中，我们都在使用ALM。因此，我们促进了从开发到测试/生产模型的结构变化。有时，我们的开发/测试模型会弄乱数据，这导致我们无法进行适当的测试。为了避免这种情况，我们有时会删除DEV/测试模型（在所有更改都与生产同步之后），并创建新的DEV/TEST模型作为生产的新副本。这的不足之处在于，与其他模型或其他模型的所有连接都丢失了，需要重新定义（源模型中的编辑映射）。与在DTAP街上促进更改相似，这确实很方便您也可以将数据推向DTAP街的下游。我可以想象，如果模型在相同的修订标签上，这只有（从技术上讲）才有可能，但是这根本没有问题。 ... 查看更多