Hi what is the row limit of data that can be presented in a table? we noticed when data is too large it shows an error message instead of prompting that data is too large.

Table Row Limits in GoodData Cloud As of the latest update, GoodData Cloud has raised the maximum number of rows in query results from 100,000 to 500,000. [Increased Row Limit] Tables can now render and export up to 500,000 rows to CSV/XLSX. Additional Limits to Be Aware Of Beyond the row count, there are other limits that can cause errors with large datasets: • Dimension with metrics (columns): Limited to 1,000 elements. This typically applies to the number of columns when metrics are displayed there, or rows if you pivot the table. [Pivot Table Limits] • Dimension without metrics: Limited to 100,000 elements. • Pivot table bucket limits: ◦ Up to 20 metrics (if Columns attributes are used) or 100 metrics (if Columns bucket is empty) ◦ Up to 20 row attributes (if Columns are used) or 50 row attributes (if Columns bucket is empty) ◦ Up to 20 column attributes [Pivot Table Limits] Regarding the Error Message When these limits are exceeded, GoodData returns a

400 Bad Request

error (e.g., "The limit for the maximum size of the dimension with metrics was exceeded") rather than a user-friendly prompt. This is a known behavior — the error appears in the visualization or can be inspected via the browser's network/console tab. If you need to retrieve data beyond these limits, GoodData recommends accessing the data via the API instead. [Raw Data API Limits] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups. 👀 Our Support team monitors all messages and will jump in if needed.

the report thats breaking has 19k rows so it doesnt seem to be due to the limit

Hi Pouyan. If you could send a link to that table, I will take a look to find the root cause of the problem. Feel free to share sensitive information via DM.

Could you please also describe your workflow that leads to that error and share the relevant trace ID?

the hire date is breaking it not sure why, if you remove it from the rows then it works again

Thank you for the details. I used our admin user to check your table internally and can confirm the row count is not the issue here. The problem is specifically with the Hire Date field. Looking at the response data, we can see an invalid date values:

"-1-11-30"

for a day,

"-1"

for a year,

"-1-4"

for a quarter, and

"-1-11"

for a week. This malformed date (with a negative value) is the most likely cause of the visualization failing when Hire Date is included. GoodData cannot correctly process it as a date, which is why removing the field from rows makes the report work again. Please try to fix the incoming data from your side and let us know if it helps.

thanks for checking!