Use conditional formatting to dynamically display a text badge on shape based on its swim lane

Hi @Cameron G, thanks for posting in the community! Unfortunately, it’s not possible to create a conditional formatting rule based on a shape’s parent swimlane.

However as a workaround, you can add custom shape data to the shapes in each lane. Once that is added, you can use conditional formatting to reference the custom shape data. I’ve added a GIF demonstrating this:

Alternatively, you can customise the colour of the swimlanes to help you quickly identify which lane you are working in. You can do this by selecting the individual lanes and changing the lane colour under ‘Advanced Options’ in the right contextual panel. See the GIF below for an example:
 

I hope this helps. Feel free to let us know if you have any questions - we’re happy to help! 🙌

Thank you, @Leianne C. I wish I wasn’t already familiar with those approaches, but I appreciate you putting together the quick informative demos - so hopefully that’s helpful for someone! 

My biggest issue is that it seems the specific swimlane name isn’t exposed. =CONTAINEDBY lists all the lane names ( e.g., [Lane 1 Lane 2 Lane 3 Lane 4] ), but so far I am unable to discover the specific one. I find this odd because it clearly is a child of the parent swimlane or it wouldn’t stay within its bounds when scaling or moving them.

Is there a way to capture the parent’s swimlane name in code?

Again, thank you so much for your help!

Thank you for sharing some additional information, @Cameron G! Unfortunately, this is not currently supported in Lucid, and the best workaround in the meantime would be the coloured lanes or custom shape data methods. 

However, I can certainly see how it can be helpful when working with very large diagrams and will convert this post into an ‘Idea’ post for our development team’s consideration. Check out this post for more information on how feature requests will be handled moving forward. 

We appreciate you taking the time to share your feedback and use-case. Let us know if you have any additional questions. 

I’ve opened an “idea”. Hopefully it sees the light of day!

Please vote to have CONTAINEDBY include Swimlane name

Thank you,

Cameron

Hi Cameron! Thank you for creating an idea post for this! I’ve just shared an exciting update in that post and will also add it here for any users who come across this post 🙌
 

We now support containment conditional formatting for swimlane lanes! On the contained shape, try using formula CONTAINEDBY($SWIMLANELANE)[1].$id to get the lane's ID, then use CONTAINEDBY($SWIMLANELANE)[1].$id = "(*desired lane id*) as the formula in the if-statement for conditional formatting.

This is fantastic! Thank you!

Also, you can get the actual name of the swimlane with the following:
=CONTAINEDBY($SWIMLANELANE)

Thanks for sharing the tip, Cameron! Feel free to let us know if there’s anything else we can do to help :) 

Hi @Cameron G! I’m Abby from Lucid, reaching out because I think you, and others who might come across this topic in the future, might be interested in Lucid’s Data Trusted User Group. This group is made up of knowledgeable users who regularly analyze and visualize data in their work. As part of this group, you’ll have the opportunity to connect directly with Lucid’s product team, gain early access to beta features, and share insights about your needs, shaping the future of Lucid’s data solutions 🎉 You can learn more and request to join here. Thanks!

​@Abby S ​@Leianne C

We have an issue with consistent results when using multi-dimensional swimlanes.

For demonstration purposes, here’s a quick multi-dimentional swimlane with the horizontal swimlane for Development and a vertical swimlane for Backlog. 

THE PROBLEM:

The index order of the returned array of the swimlanes the shape is contained within flipflops for no reason (that I can figure out). e.g. I see it as [Development,Backlog] and another person I’m collaborating with sees it as [Backlog,Development] (notice the order is different). 

Example:

{{=CONTAINEDBY($SWIMLANELANE)}} returns:

[BACKLOG,DEVELOPMENT]

However, someone else views the same document and their array is:

[DEVELOPMENT,BACKLOG] (notice they’re reversed)

So, if I wanted to ONLY display the horizontal swimlane header and not the vertical header it will randomly switch between them: 

{{=INDEX(CONTAINEDBY($SWIMLANELANE),2)}}

That means for one user, the label would say “DEVELOPMENT” (correct) while the other sees “BACKLOG” (incorrect).

Is there a way to guarantee the order is consistent or to ONLY get the header values of either the horizontal or vertical swimlane?

Hi ​@Cameron G, thank you for continuing this thread and sharing detailed information about the issue you’re experiencing. I’d love to take a closer look at the example you shared.

If possible, could you please share the temporary Support PIN for this the example document? This will allow me to take a closer look at the issue you’re experiencing.

For more information on generating a Support PIN, check out this Help Center article. This Support PIN doesn’t allow anyone but Lucid Support to take a look at your document, so you are safe to post it here.

Let me know if you have any questions, thank you!

​@Leianne C : I actually had a conversation with ​@Richard U this morning about this issue. Please follow up with him. If you have additional questions regarding the issue PLEASE reach out as this bug needs to be fixed. Thank you!

​@Leianne C , ​@Richard U :

Support PIN for sample document showing the bug: duR0tjf9XAkqWo179915220

Hi ​@Cameron G, thank you for following up and sharing the PIN! I have connected with my colleague Richard and will share any updates about this in this thread. 

We appreciate all your help and patience. Please feel free to let us know if you have any further questions in the meantime! 

Quick update here! This issue had been filed as a bug. 

We apologize for any disruption this may cause, and we will update this thread with any new information about a fix. Please follow along on this thread for updates, and post any additional questions or concerns below.

Appreciate your support. Fingers crossed it gets fixed sooner than later. 

Thank you!

This is great news!!! Thank you so much!!!

Of course ​@Cameron G! Please let us know if you have any other issues that come up!