Skip to main content
Tutorial

🔢 Lucid expert tip: Auto-numbering branching paths in process maps

  • June 24, 2026
  • 1 reply
  • 24 views

Forum|alt.badge.img+6

Numbering a straight line is easy, but what happens when your process splits? This video explores how to use page data and upstream formulas to ensure your step numbers remain accurate even across complex branching paths. For full formula information, please refer to this documentation, and for a similar tutorial on numbering shapes in a more basic path, please view this post:

 

What you’ll learn:

  • How to create a custom data property at the page level to manage global numbering logic.
  • How to write if formulas that count upstream shapes to automatically determine the correct step number.
  • How to handle branches so that parallel steps share or increment the correct subsequent number.
  • How to use conditional formatting to display these dynamic values as professional text badges on your shapes.

⚙️ A note on the UI

This video was produced around 2024. While the Lucid interface has been refreshed since then, the formula logic for upstream counting and the conditional formatting engine remain the standard for building intelligent diagrams.

Do your processes have a lot of "if/then" splits? Tell us how you're keeping your complex maps organized in the comments!

 

Comments

Cycling Scott
Lucid Legend Level 2
Forum|alt.badge.img+3
  • Lucid Legend Level 2
  • June 25, 2026

As a process guy, I would never want to have ambiguous Step Numbers in a flowchart. In your example, you have two 4s and two 8s because of branches.

Can you suggest a way to ensure there are no duplicates?

Perhaps:

  • Tracking the current max step number in a page data field so new shapes are +1?
  • Checking one step downstram and if the count isn’t zero then finding the max on the page and incrementing it by one to number a new shape?
  • Something else entirely???

I realize that any option to ensure uniqueness complicates the forumula, but uniqueness is essential in many cases.

Also, while it’s nice in a simple flowchart to have neatly sequential numbers from beginning to end, that doesn’t really matter; it’s uniqueness that’s important.