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.
... View more
Hi, Couldn't find a similar pre-existing idea, hence the post. The conditional formatting on KPI cards or Grid cards in NUX has been very useful. I am keen to see the color range options in the formatting to be expanded further and include the Hex Code (RGB) range, similar to what we have in Chart cards. This can be useful while building visulisations catered to the customer's branding. For now, you have to use the existing 4 ranges.
... View more
Please consider this feature as it will really help with input validations. Simple conditional formatting or access to manage notifications will be essential. I like following way of highlights and would like configure it for myself as well
... View more
Hey all, I just helped a customer dealing with this same issue, so I figured I would give a general overview of what is happening in this situation. Hopefully this resolves all current and future questions people have. There are two main factors at play in this situation: 1. Why it does not happen to Workspace Admins: During an import, Workspace Admins have a special ability to affectively 'ignore' Selective Access on the target. This is intended - there are situations in which a Workspace Admin should have limited view access (with sensitive data like HR salary information) however the base data still needs to be imported. A user does not have this ability, so in general if they try to import items without the correct Selective Access, those items will fail. 2. What is happening that causes this error for Users: This error and ones like it are completely caused by List level Selective Access. As a test, if you remove Selective Access from all lists in your model then have the user attempt the action, they will be guaranteed to not see this error. But obviously Selective Access is necessary, so here is how to understand what is happening: This error can occur when creating a new item or modifying existing ones: A. "You are not authorised to move item to parent: <X>" - when the Parent specified for the parent is one that the user does not have Selective Access to. These errors only occur when the item already exists: B. "You are not authorised to update this entity" - when they do not have Selective Access to the existing item and are trying to change something other than Parent. C. "You are not authorised to move this entity" (the one in question in this post) - when they do not have Selective Access to the existing item and are trying to change the Parent value. The lack of Selective Access described here can be caused by not having access to the item itself, or the item's parent, or if the item has no parent. Even though we cannot obtain the same error exactly as a Workspace Admin (due to reason #1), we can still troubleshoot - set your Selective Access to be the same as the User, and view the list dimension somewhere in a module or dashboard (NOT in the settings area, as this will display all items regardless of Selective Access). You will not be able to see whatever item or parent the user is attempting to update. That is the root cause of the issue - figure out how to either A. give access to the appropriate item, or B. not include that item in the users import. One thing to note: The last two errors cannot occur when creating a new item. If you thought that the item did not exist or had been deleted or something but the non Admin user is receiving this error, then go to the settings area and search the list for that item - what is most likely is that the item still exists and has become an orphan item because the parent was deleted. They are displayed at the very bottom of the item list, and do not role up to the 'Top Level' item. If Selective Access is in place then end users will not be able to modify records that do not have Parents in a hierarchy, causing the error. In this case, it may be good to have an automated 'Delete from List' action that removes any objects that do not have parents or something similar. As a summary - the error message is not an Anaplan bug but intended behavior when Users try to update or move items to which they do not have Selective Access. A Workspace Admin will not see this error because they have an intended exception to standard access rules when running imports into lists with Selective Access. That should help clarify this issue for others encountering it. If you are still encountering issues or confusion with this error, please open an Anaplan support ticket and include a link to this article/comment as reference.
... View more
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).
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:
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:
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.
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.
... View more
Yes, makes sense. Thanks. I have always thought of LOOKUP to be more Module/Line Item centric and SELECT to be List/List item related. It is good to know that they work on the same principle.
... View more
Hi, @sandeep_bk is right, everytime you create a new line item that you want to import to, you can reuse the existing import action but you do need to remap by doing 'edit --> Line item tab'. Another thing that i would like to point out is that it's not best practice to have subsidiary views for input fields. Ideally all the line items would have the same lists combination as the module, but it's very hard to do so for calculation line items. However we should build a separate module for input line items which share the same lists combination. Off the top of my head, one reason i can think of why this is a bad idea is the severe limitation of Filtering. You'll see in the screen shot below that the line item can only refer to itself for filtering purpose. Thanks, LipChean
... View more