Have report validation warn when a change will cause a collision of field names with already existing ad hoc fields

Recently we released a new field. Unfortunately we didn’t realize that the same field name was already being used in a legacy dashboard for an ad hoc field, so it broke the widget. I don’t think there’s any way to search for these errors either, or to search for all instances of ad hoc fields with a given name in legacy dashboards. The reporting validation didn’t raise any errors either or tell us that there would be a naming collision. We would LOVE if reporting validation could check for collisions of duplicate names and tell us what reports will break due to that so we can preemptively fix it before releasing.

Hi @anya.conti sorry for the late response. Somehow we missed this. Just wanna say that we’re looking into this issue, and thank you for your report!

1 Like