Hello, I'm getting a weird error that won't let me edit the name of a metric within a chart. I see in the error that the label doesn't exist despite it existing in the platform. Traceid: "30b97645ac0dcf225e6c46599b5bfedc"

Could you please provide a link to the chart in question so we can access it with the admin account? You can DM me the link if you'd like

the metric is directly from the the redshift table. the only thing I can think of that happened is I renamed it in the Logical Data Model and that ended up breaking it in the visualizations. I've done this before on other dashboards and it wasn't an issue though.

I'm not sure this is supported behavior, but I'm going to escalate this further to our L2 technical support engineers for further investigation.

Hey @Mark Dilson, Francisco from the L2 Team here. I investigated the visualization that was giving you trouble, and found the issue. I impersonated our technical admin user and used the APIs to check the visualization itself. On its definitions, I located a few

attributeFilterConfigs

, which are used to list the labels of an attribute filter. These configs didn’t match anything on the visualization or on the LDM, so I think they were remnants of a previous configuration of the chart, where attributes with labels were being used in the filters. You mentioned a change in the LDM, which could help explain it - these attributes/labels were removed, but for some reason were still mentioned on the chart’s definitions. I’ll be running some tests on my end to try and reproduce it properly. In any case, I took the liberty of removing these extra objects from the chart’s JSON definition, and after testing can see that renaming the chart now works. Please give it a shot and let me know how it goes!

@Francisco Antunes thank you for fixing this. it works in that one dashboard, but seems like I'm getting a similar error now for another dashboard I tried doing this in both the dashboard and analyze sections of the platform. I believe an issue is going on if you edit the data model naming of the fields, it breaks the charts. Would think this shouldn't impact it other than appear wise, since the id doesn't change. If I rebuild the charts from scratch though, it ends up working. > {detail: "Some of given referenced 'labels' entities do not …rce)/Workspace(b9025f9f1b7f4bd3a197003c9ee5a289)]", status: 400, traceId: '93e60554b0b6a3eda6d411bd574bd149'} > detail > : > "Some of given referenced 'labels' entities do not exist. Not existing IDs: [Identifier(gooddata_lqvision_alloy_data_source.data_source)/Workspace(b9025f9f1b7f4bd3a197003c9ee5a289)]" > status > : > 400 > traceId > : > "93e60554b0b6a3eda6d411bd574bd149"

Hi @Mark Dilson - sorry about the delay. So I understand you were able to get it working with the suggested syntax - but you identified that the issue might be caused by changing the model naming of your label fields. That makes sense - I will run some tests to establish how the API objects for the labels interact with the visualizations/dashboards. It might be as intended, but I will let you know 🙂

No worries. Thank you for looking into. Just something to flag as it seems like it would be a nice thing to be able to change the field names in the LDM without it breaking the charts that already exist. Especially since the only way to fix it is recreating the charts from scratch or reaching out to support to help fix on the backend.