Transitioning Calculated Metrics from Positional Indexing to Unique Layer IDs

I’d love to see the BrightGauge development team move from positional indexing to Unique ID referencing for multi-layer gauges.

Currently, when we build sophisticated gauges with multiple layers and calculated metrics, the formulas appear to be tied to the layer's order (1, 2, 3). If we need to remove an intermediate layer or reorder them for better visual clarity, the "link" to the data often breaks. This requires us to manually re-map the calculation pills to the new layer positions.

I believe moving toward persistent ID-based references would benefit the entire community by:

• Improving Reliability: Reducing the risk of "broken" dashboards after minor maintenance.
• Encouraging Innovation: Allowing us to experiment with more complex, multi-layered data sets without fear of "breaking the logic."
• Saving Time: Freeing up MSP admins to focus on data insights rather than gauge troubleshooting.

Does anyone else run into this when refining their reporting? I’m curious if others have found creative ways to manage layer dependencies, or if this change would help your workflow as much as it would mine.