Having an issue where I am trying to refer to a csv dataset but I can't save any metric that uses it,

Hey Chris, thanks for reaching out. May you please share a direct link to the workspace to allow us investigate this further. You can send it to this thread or via dm, whichever works best.

Ok that has worked now not sure why it didnt before

Glad to know this works. This was probably caused by a minor glitch like a connectivity issue with the data source or a temporal hiccup in our infrastructure. Apologies for any inconvenience caused.

Hi its started doing it again with either of the data sources I have in there

Hi Chris, kindly share the error Id to allow us troubleshoot this further. You can get the error/traceId from the dev console. Let me know if you need further assistance.

it doesnt give me an error id when it happens i jhust get a red box pop up saying save error

Hi Chriss, I am actually checking, using our Admin user and I can not manage to see the error. But I am looking currently in our logs.

That worked but I don't have another metric called that in this workspace

Perfect, I will check the objects if I can find the related id

Metric was created using the Metrics tab, I then realised an issue with the dataset so I deleted it to recreate it. with that the metrics associated were no longer showing

Can you tell us which issue with dataset? if you go to Edit, I can see there is a warning in a dataset, related with the mapping of a Date attribute. We are just trying to reproduce the issue.

oh no it was just a CSV dataset and I realised I had missed a column the issue isnt there at the minute

Hi Chris, allow me to jump in here. You mentioned that the issue is not there at the moment, does this mean its working just fine? Are you now able to create metrics after fixing the column issue in the CSV dataset?

I am able to create metrics but the issue seemed to be that after I deleted the dataset and reuploaded when I went to create a metric I would use the same name I had previously but the ID must have still been sat in the background somewhere even though I couldn't see it

Hi Chris, after running some tests, we were able to reproduce this issue. We have escalated this to our internal product team to find out if this is expected and to analyse the root cause of this. However, please note that no specific timelines can be shared at the moment. Our team will update you as soon as we get feedback on this. Thank you for understanding. Feel free to reach out to us if any issues come up in the mean time.

Hi Chris, the metrics disappeared from the UI, but there are empty shell definitions in the backend, therefore, when you are creating a "new" metric with the same name (id), you will not be able to save it, since according to the Platform, the metric already exists. There are two ways to go about this: 1. You can remove the metrics altogether by: Listing all the metrics in the workspace from the following endpoint: /api/v1/entities/workspaces/aw_test/metrics And deleting the orphaned metrics, by doing a DELETE call on the object: https://www.gooddata.com/docs/cloud/api-and-sdk/api/api_reference_all/#operation/deleteEntity@Metrics https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1702919910308869 2. You can revert the LDM changes that led to the breaking of the metric. This behavior can also occur when the LDM is modified in a way that causes cascading effects, which can break existing metrics and other workspace objects such as dashboards. I recommend ensuring that any changes you make to the LDM do not impact actively used objects, such as metrics, dashboards, insights, etc. For example, when removing attributes or facts, be sure to double check the warning message listing the consequences. For more details, I am also linking a thread were this was discussed previously. Let us know if you have any questions.