Best Of

Re: The three most useful applications of the data write action

Thank you @MikhilA for this great article to discover New UX functionality.

Having action to update current date is good but for data traceability purpose still need time stamp with granularity level like hour:min:sec. Hope this functionality can be added into model and added to Process so no need to manually click separate button for update date.

sarahputrikag

1

How I Built It: Flagging hierarchy list levels

Author: Timothy Peterson is a Certified Master Anaplanner and Senior Delivery Associate at Spaulding Ridge.

Greetings Anaplan Community!

Hello and thank you for checking out my ‘How I Built It’ tutorial. In this video, I will showcase how you can leverage ratio and formula summary methods to flag different hierarchy list levels.

I will demonstrate examples of how flagging hierarchy list levels can be used to improve the user experience on UX pages and provide a detailed walkthrough of how the examples are set up in the back-end model.

There are many uses for being able to identify and flag individual hierarchy levels. The three examples I will cover are:

Applying conditional formatting to highlight specific levels of a hierarchy list.
Easily applying alternate aggregation methods to the top level of a hierarchy list.
Allowing users to quickly and easily show or hide different levels of a hierarchy list.

Check it out and let me know if you have questions!

https://play.vidyard.com/Y3hWUFWP2vnoCu2iD6Ws4y

……..

View all 'How I Built It' tutorials here.

TimPeterson

13

Re: NEW UX: Insights and Quick Links on Board Views

This is something we absolutely want to add to Board pages in the UX. Unfortunately we don't have capacity to add in early 2024 due to other priorities but its something we would love to add in the second half of the year.

Glad to see there is so much interest in this addition.

sprender

2

Re: Master data and transaction data data hub in workspace

@Srivaths123

Lots of directions you can go with that. Here's a couple of thoughts which really comes down to how much security you need.

The advantage of partitioning a workspace for the data hub is for segregation of duties and to add an additional layer of security. Each workspace can have it's own set of users so you would only allow people access that help administrate the data hub.
If you must have a separate data hub for each horizontal, i.e. finance, sales, supply chain) then consider creating three models in the partitioned workspace. I would only suggest separating the models if there is a security concern though. For example, the data integration modeler in charge of Finance shouldn't see the data hub for sales. Otherwise, one big data hub is better so you can reuse some of the master data, for example the time properties.
As a last resort, if you absolutely must segregate the data hubs for each horizontal, you can create three separate workspaces. I would not recommend this as any common data will have to be constantly synchronized.

Hey, just some thoughts. You might also consider creating a pros/cons grid and really think about what you're signing up for. Overall, my experience has been that keeping the models as simple as possible is best. Once you have integration points all over the place, it becomes a support challenge and quite a burden.