Just uncovered a use case that should be easier to resolve.
I created a custom field a long time ago that some other admin added to a report. We no longer use the field. I was going to delete it but was unable to because the field is being used in a report. Without calling Absorb Customer Support and having them send a ticket off to a developer to trace the origin of the report based on its name—a laborious practice—I have no way to know who created the report aside from manually searching every admin I've ever had in the system.
In my particular case, I had to create a ticket with the name of the report that the custom field is part of, wait for a developer to identify the user ID for the person who created the report, then go in and impersonate the user to delete the report. Going through the process has taken several hours and multiple emails/ calls into Absorb.
Seems like there should be an easier way to delete a custom field–even if it’s part of a report someone else has created. Or, at a minimum, Absorb should identify in the error message the person who created the report that the custom field is part of so I can solve the problem on my own without having to put a trace on the user.
Thanks!
Thank you for taking the time to share your idea with us. After careful consideration, we’ve determined that we are unable to prioritize this suggestion at this time. While we recognize the value of your request, our current roadmap commitments and resource constraints prevent us from pursuing it in the near future.
Please know that your idea remains in our repository, and we will revisit it as we continue evaluating improvements to reports and custom fields, specifically the ability to delete custom fields that are no longer in use.
Your feedback is invaluable in shaping our platform, and we truly appreciate your contribution to its growth.