Hi GD Team, We regularly need to produce tables that have between 50-100 columns, mostly string fields. The current max columns is 50 correct? Is there a way to get beyond this limitation?

Great questions! Let me address both topics: 1. Table Column Limits The 50-column limit you mentioned is outdated. GoodData Cloud has significantly increased table limits: • As of November 13, 2025, tables and pivot tables now support up to 2,000 columns and 1 million rows, thanks to improvements in the cross-tabulation engine. [Support for More Columns] So your requirement of 50–100 columns is well within the current limits. You should be able to build those tables directly in GoodData Cloud without any workarounds. Note that pivot table bucket limits still apply (e.g., up to 20 metrics if Columns attributes are used, up to 20 column attributes, etc.), so the exact configuration may matter depending on how your table is structured. [Pivot Table Limits] 2. Auth0 ID Visibility After User Creation You're correct that the Auth ID is not visible or editable in the GoodData UI after a user is created. However, it is fully accessible via the API: • Retrieve all users (including their

authenticationId

):GET https://your-hostname/api/v1/entities/users • Retrieve a single user:GET https://your-hostname/api/v1/entities/users/{userId} • Update/correct the Auth ID if needed:PUT https://your-hostname/api/v1/entities/users/{userId}(Include the new

authenticationId

value in the request body.) This means you can pull Auth IDs programmatically for auditing and verification purposes, even though the UI doesn't expose them post-creation. [Users API] 👍 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.

Hi Greg, can you confirm if you are currently having an issue related to this limit? If yes, please feel free to share more details with us and we will help further.

Hi Mauricio, I thought the limit was still 50 rows because when I am creating a table, the UI will not let me add more than 50 rows and the documentation also says 50. Maybe there is some setting I have to activate in order to go beyond 50 rows?

Hi Greg, thanks for the screenshot — that's the right table, and it explains the mix-up. We apologies for the initial confussion. Those are bucket limits, not table dimensions. Attributes you put in the Rows bucket each render as a column in the resulting table — so "50 attributes in Rows" isn't a 50-column ceiling. With the Columns bucket left empty you can combine: • Rows: up to 50 attributes • Metrics: up to 100 metrics which gives you up to ~150 columns in a single table. (If you put anything in the Columns bucket, both caps drop to 20 — so for a wide flat table, leave Columns empty.) To make sure we point you at the right approach, could you tell me a bit more about what you're building? 1. Roughly how do your 50–100 columns break down — how many are attributes vs. metrics, as a row or as a column? 2. Are you building this in Analytical Designer, or via the API / embedded SDK? 3. Do you see some error in the UI, is there any traceId?

Hi Mauricio, yes I am using analytical designer and I hit the 50 attribute limit in the ROWS bucket. I actually do not have any metrics most of the time. Many of our clients have CRM databases with several small tables (8-10) and they ask me to combine the attributes into 1 larger table (50-100 columns, 1 row per CRM customer) for them. I can easily pre-join the data in either SQL or the GD data model but cannot find a way to make the output available to them via a table in Gooddata.

Hi Greg, thanks for confirming — that explains it. Since you're not using any metrics, the combined limit doesn't apply here: with attributes only, 50 in the Rows bucket is currently a hard cap for a single table insight in Analytical Designer. Two ways around it: split it into two table insights (up to 50 attributes each) side by side on a dashboard, or pull the combined dataset via our raw data API instead of building it as an insight — specifically

POST /api/v1/actions/workspaces/<workspace_id>/execution/afm/execute

(docs: gooddata.ai/docs/…/access_raw_data_through_api), which isn't limited by the 50/20/100 bucket caps, just by overall result size, well above what 50–100 string columns would need.

Hi Mauricio, yes please submit this to your product team to increase the max of the row bucket (columns) of the pivot table to 100. If not possible, perhaps a new visualization being a normal table (not pivot) that could have 100 columns. This would then match closely to what I can do with Google Data Studio which has both a normal table and a pivot table. Their normal table allows 100 dimensions and 100 metrics. Their pivot table has metric and row limits similar to your pivot table. Thx.

Hi Greg, Thank you for bringing this to our attention, and I apologize for any inconvenience it may have caused. I want to let you know that we have shared your request with our Product team. While we cannot commit to specific timelines or provide updates on roadmap decisions, we appreciate you taking the time to reach out. Please don't hesitate to contact us if you need any further assistance.