This message was deleted.

Related feature requests for the Metrics overview page, it would be great to have: • Filter by Project or Data source • Bulk-edit (change project, archive, delete)

Thanks David - we'll take a look

Hi @fresh-football-47124! Any news on this? We would like to delete a data source, and ~400 metric is connected to it, which are already archived. Can we somehow delte them all? Thank you! 🙂

Hi Anna, Good morning and thank you for your response. As you are aware, to switch a data source, you'll first have to remove the metrics, and then re-add the metrics to the new data source. I will have to be the bad news bear here as unfortunately, this isn't the best UI design on our end (I apologise for that), as currently the UI does not have the functionality to bulk delete. That being said, we do have the functionality to bulk delete metrics by leveraging the REST API - you can use the REST API endpoint ​`DELETE /metrics/{id}`​. Let me walk you through how to achieve this: 1) Send a DELETE request to the endpoint ​`/metrics/{id}`​, where ​`{id}`​ is the ID of the metric you want to delete. 2) The ​`id`​ parameter is required and should be included in the URL. It represents the ID of the metric you want to delete. 3) The ​`Accept`​ header is optional and its type is string. Here is an example of how the request might look like:

DELETE /metrics/{id}
Accept: application/json

In the above, please replace ​`{id}`​ with the actual ID of the metric you want to delete. The server will respond with a status code of 200 if the operation is successful. The response will be an object, but the schema is not specified in the documentation. Please note that this operation does not require authentication. For deleting a fact metric, you can use a similar endpoint ​`DELETE /fact-metrics/{id}`​. Please refer to the ​*GrowthBook REST API documentation*​ for more details. In parallel to the above, you may wish to upvote this public facing feature suggestion for the ability to bulk delete via the UI here. Hope this helps and please let me know if you run into any issues when running the API, we are on hand to help debug :)

Hi @flaky-noon-11399 thank you for your help! 🙂 Unfortunately API would be more difficult at this time, but I will keep in mind this solution. And also good to know to not to look further on the UI! 🙂 Thanks again!

Hi Anna, it was my absolute pleasure to assist and sorry I dont have the best of news about this functionality being available on the UI 🙈 If you later want to revisit the API route we can help debug any blockers you may face. We are on hand to help 🌼

Thank you! ❤️