Below is the logical data model GoodData #gooddata-cloud

Join Slack

Below is the logical data model

# gooddata-cloud

Anjali Mandowara

08/05/2025, 10:15 AM

Below is the logical data model

Yvonne Changamuka

08/05/2025, 11:30 AM

Hi Anjali, thanks for reaching out and sharing the video. Could you please share a direct link to the report so we can investigate further? I will run impersonation to try and see what could be causing this. Feel free to share the report via dm.

Anjali Mandowara

08/06/2025, 7:03 AM

https://wizehive-zengine-dev.cloud.gooddata.com/dashboards/#/workspace/b78fc034b60d4e8199e63fd7d8af88f[…]hboard/2263d86a-8ef7-413e-a4a4-837ffc561711

Yvonne Changamuka

08/06/2025, 7:44 AM

Hi Anjali, thanks for sharing a link to the report. Please let us review this and we will get back to you with more details as soon as possible.

Anjali Mandowara

08/07/2025, 8:56 AM

@Yvonne Changamuka any update?

Yvonne Changamuka

08/07/2025, 9:04 AM

Hi Anjali, I’ve been able to reproduce the issue on my end, which is a helpful first step. I'm currently continuing the investigation to identify the root cause and determine what might be contributing to the behavior you're seeing. Please be assured that this is being investigated, and I will share updates with you as soon as I uncover more information or have any meaningful findings to report. I appreciate your understanding while we work through this.

Yvonne Changamuka

08/07/2025, 2:04 PM

Hi Anjali, Thank you for your patience while we reviewed the issue. After taking a closer look, it appears that the behavior you're experiencing could be related to how your Logical Data Model (LDM) is structured. We're continuing to investigate this further to better understand the root cause. In the meantime, as a workaround, you can display the data using the attribute and fact in question by enabling the “Show missing values” option in the Analytical Designer. This should help surface the expected results while we dig deeper into the underlying issue. For more context on this, I will share a screenshot via dm.

Francisco Antunes

08/21/2025, 10:03 AM

Hi @Anjali Mandowara, thanks for hanging in there while we investigated this in more detail. I’m Francisco, from the Technical Support Team. So I checked the issue further and have found what’s causing it: the column

Funder to Fund Amount

is displaying numbers in unexpected numerical notations (e.g.: scientific notation, or floats). In GoodData Cloud, it is recommended that Fact objects are in NUMERIC-style data types (see our Documentation on the subject). I see that the column is in INT. I am currently investigating what is causing the values to show up in these different notation types. Are they displayed like that in the data source? Or are they just very large numbers? Meanwhile, you can work around it by ensuring that the Metric has no rounding on its formatting.

Francisco Antunes

08/21/2025, 4:08 PM

Hi @Anjali Mandowara I investigated a bit further and was able to figure out the Data Type on the data source (Postgre) - it’s set as

double precision

, which is not one of our supported data types. It got identified as INT, which is incorrect (as

double precision

and other float data types have decimal numbers, which INT does not). The solution here is to make sure that these fact columns are CAST as a NUMERIC (or other accepted format - refer to the documentation I posted earlier) before they are loaded into GoodData Cloud. A view would be a great way of achieving that - and it can even be done directly as an SQL Dataset. This will ensure that only numeric values are loaded in, and avoid the problem.

6 Views

Open in Slack

Previous Next