About shreyak.garg

Hi, The notification action in the UX pages seems to be improving with the introduction of sending it to users based on module data. It would be useful if we could limit the security on these notification actions so that random users do not run the action accidentally. For now, an alternative is to create the same dashboard twice and remove the notification from one of these DBs so that the unwanted users do not run it. ... 查看更多

Don't think a similar idea has been posted previously. In TEXT cards, it would be great if we can change the following: 1. The heading colors to be Hex Code (RGB Range) based so that there is a variety of options that caters to branding requirements. 2. Similar to how Image cards and links to other pages work, it would be ideal that we can click on the heading text and it takes to the linked page - rather than clicking on the top left '>' link in the Text card. ... 查看更多

嗨，找不到类似的先前想法，因此该帖子。NUX中的KPI卡或网格卡上的条件格式非常有用。我渴望看到格式中的颜色范围选项，以进一步扩展并包括HEX CODE（RGB）范围，类似于我们在图表卡中所拥有的范围。这在构建符合客户品牌的构造愿景时可能很有用。目前，您必须使用现有的4个范围。 ... 查看更多

Can't find this as an existing idea! It appears that Field cards are always editable. I find that Field cards sometime make more sense when added in a bunch (compared to KPIs) and also look better to show some System Mapping fields. However, it is not ideal that the users are able to change these mappings. Can we have the ability to not edit Field cards (similar to DashGrids etc.)? ... 查看更多

随着新UX中新的Notificaiton功能的引入（在测试时效果很好），将其扩展到包括“ Anaplan角色”而不是在电子邮件选择中包括特定人员将是很棒的。另一个遥不可及的扩展是将其与广告组等集成在一起，以将整个组织的通知发送给对Anaplan访问权限有限的人！ ... 查看更多

With the introduction of the Notification action in the New UX, it would be great to have the ability to edit these actions once created. At the moment, once the notification worksheet action has been created there is no ability to tweak it further - you have to redo the whole thing again. ... 查看更多

Technical Summary Statement The objective of this article is to compare values in a TEXT formatted line item and identify the values that occur more than once (duplicates). Problem Statement Sneakerz is an up-and-coming shoe company with a variety of shoe brands in its brand portfolio. They are expanding internationally after having started from their humble origins in countryside Australia. As part of their international strategy, the marketing team is coming up with new ideas for brand names. Sneakerz uses Anaplan for Connected Planning across the organization. The marketing team wants to enter the new brand names in Anaplan and expects Anaplan to highlight the duplicates. For example, if ‘Comfort’ is entered on two separate rows, Anaplan should highlight the second one as a duplicate. Final solution should look similar to the following: Solution Create an input module “INP01 – Brand Names” that allows a user to enter the New Brand Name as an input. Create a new line item ‘ Valid Name?’ . This will check that the New Brand Name is unique across the numbered list (and highlight if there is more than one occurrence). The formula for the line item is as follows: Note : The formula above ignores the blanks (if no input is entered). If you want to use conditional formatting to highlight the duplicate texts, then continue reading. Add a line item ‘Cond Format | Not Unique?’ to indicate second or more occurrences in ‘Valid Name?’ line item using conditional . Ensure that the Summary Method is set to ‘None’. Go out of the Blueprint view. The module should look like this: Optional : Use the Conditional Formatting feature to highlight the duplicate occurrences in the New Brand Name field. The final output is shown below: Conclusion The final output view indicates that there are three New Brand Names that are duplicates namely – Comfort, Ethical, Futura. On the other hand, two New Brand Names – Runner and Bambino are unique in the data set. Pitfalls of this Approach The limitation with this solution is that you can only identify the successive duplicates and cannot tag the first occurrence as a duplicate value too. Other Suggestions Always follow best practices and turn off summary calculations if not necessary. Rename and organize modules in relevant functional areas. Avoid Daisy Chaining in the calculations if they can run in parallel. ... 查看更多

Hi, Not sure if this idea has been posted before! I would love to have the ability to apply conditional formatting to field based cards in the new UX. It would be a good way for a user to visualise if they haven't entered a required attribute for a list item! At the moment, the alternative is to use a grid card with the view having conditional formatting - but that doesn't look good in the new UX. ... 查看更多

Hi team, I am keen on seeing the KPI cards advanced further to be color coded as well (perhaps based on the conditional formatting in the module views itself). For e.g. - If a KPI number represents a growth % then the color/card text background could be highlighted as GREEN or RED otherwise. This would make the UI much more intuitive and visually easy to understand. ... 查看更多

嗨，随着新的UX在客户和潜在客户中越来越受欢迎，有能力垂直将卡中心文本中心。就目前而言，它似乎以水平方式工作，然后您必须使用卡大小来使其看起来像是水平和垂直的中心。可以选择像名为“中间位置”的MS Office功能那样垂直居中，这将是很棒的。 ... 查看更多

Hi all, I am receiving an error with one of the numbered lists - "You are not authorised to move this entity". ONLY non- workspace admins are getting this error. They are able to add items to the list but they cannot put the Parent against the Parent field. I have checked the action and the Parent field is being correctly mapped in the action - as mentioned in this thread. The user has access to the source module view and is able to see the data that is being used for Parent mapping. The user also has access to the list in Roles -> List section and the Roles-> Actions section for the action being run. Also, this numbered list has a parent/child relationship and the top ancestor list in this chain has selective access. The user has Total Company access WRITE access to this ancestor (Top level element) list. Can anyone identify the issue if they have seen this before? ... 查看更多

嗨，我们有一些间歇性问题的导入操作，这些问题放弃了以下错误（在PIC中），目标模块引入了一个新的订单项，该项目与整个模块相同列表的子集。该模块基于子集1（适用于）。新系列项目基于子集2（适用于）。子集1和子集2是来自同一列表A的子集A。操作失败说目标模块中的尺寸与导入定义不符。引起该问题的动作是对模块中不同订单项的预先存在的动作，该操作没有直接链接到引入的新订单项。另外，我试图打开此预先存在的操作，将新子集设置为“不适用于此导入”，然后运行它 - 它仍然会导致相同的错误。问题似乎只有当您从头开始重制整个动作时就消失了。这将是一个问题，因为它限制了我们建模，而不必担心所有先前存在的动作/集成。 ... 查看更多