Hi all, I’ve been facing a recurring issue with the LDM that is affecting our reports. Here’s the sequence of events: 1. Initially, I made two changes in the LDM: ◦ Joined a new table. ◦ Added date fields to that table and linked them appropriately. 2. After saving these changes, I created reports based on them. 3. Later, I noticed that the first change (table join) remained intact, but the second change (added date fields) disappeared. 4. As a result, the reports automatically switched to a different date property on their own. 5. When I checked the LDM, I found that the date property I added was missing. 6. I re-added the date property in the LDM and saved it, but after doing so, the reports started failing to load. Could you please help me understand why the added date property disappears from the LDM and why the reports fail after restoring it?

Hello Aman, could you please share a link to the workspace this is related to? We will take a look and reproduce from our end.

Hi Aman, Thank you for the access. Few more questions so we can investigate this properly - could you please give us some example of these date fields and vizualisation which would be affected by that? Currently, we are not sure what to check and where exactly. Feel free to DM me if it's more feasible, please involve screenshots of these date fields. Basically, we would need some example overview what was exactly done.

Two date fields, "CCM Created At" and "CCM Started At", were added the morning before yesterday. However, a few hours later on the same day, I was unable to locate them, so I re-added them again. Additionally, some visualizations also broke during this process.

Hi Aman, I can see that these dates are currently added. Can you please try and recreate the steps so that they will disappear? Unfortunately, we cannot see anything in the logs indicating that they had been deleted

Hi, Jsoseph I have re-added the dates, but initially it disappeared thats why I have add it back. The point I have re-added the dates, it didn't break so far. Also, how I can recreate it, if that seems to be problem from Good Data side, if this happens again then only I can do it. Apart, from that there is this frequent problem of reports failing to load after saving it. One way I found if I add the broken report in Dashboard, then it loads, but in other cases it fails to load in both the sections. I don't know why it happens, due to LDM changes, note that we are not editing any existing table, we are either adding new tables or sometimes adding the date property or adding one or two property in the existing tables. Also, if I re-name the property names in the existing table inside the LDM will it break?

Hi Aman, depending on your workflow in updating your LDM and the changes you are making in regards to connections to datasets, as well as location within the LDM, you can break some reports/metrics. I'm unable to reproduce such a scenario in my own enviornment, so we would need details as to exact steps you have taken and the timestamp in which that action occurred. Then we can search our logs for a relative timestamp to when the said viz/metric goes missing. It would be ideal if you had the url for the object which goes missing as well, if possible. I would recommend going through the following documentation: https://www.gooddata.com/docs/cloud/model-data/evolve-your-model/

Hi, I went through the documentation. We are using drag and drop in the LDM for the tables that we want to use, today we added another table and connected it with the existing tables in the LDM, after clicking the save button of LDM, a message popped up that says that it will affect the following reports and there is an option of save anyway. I clicked the Save anyway option, then all the reports mentioned in that warning message are failing to load. Can you help me with this situation. Because there might be cases when we need to add tables in the LDM either from Drag and Drop or creating SQL Dataset.

Hi Aman, This all sounds like normal behavior. When you make changes to the LDM, it can have over impact on previously created reports. This depends on the changes you are making of course, and the connections to datasets that can occur. this is why there are warning messages and notifications for objects that will be affected. Please note that GoodData Support manages, break/fix issues with the platform itself. This is more related to your implementation and how you are managing your LDM. If you need help with implementations like this, our customer success team would be able to assist you further with changes to your LDM. If this is something that you would like to discuss, we can help get you in touch with your account owner.

Yeah, Can you help me connect with account owner or customer success team, who can help me out with working with LDM and future changes.

Hi Aman, I have contacted to your Account Owner, Pavel Doubek, he is aware of this and, he will contact you soon.

Sure.