A field in our Allocadia project isn't appearing as an attribute in the GoodData data table

GoodData only surfaces fields configured for analytics, with the project refreshed. Verify both, plus the field ID, then contact Support.

What this answers:

• Why a field that exists in your project doesn't appear in the GoodData (Insights) data table
• What to check on the field's analytics configuration
• When a GoodData project refresh is needed

How attributes get into GoodData

GoodData — the engine behind the Insights tab — doesn't automatically include every field from your Allocadia project. Two things have to be true for a field to appear as a usable attribute:

1. The field is configured for analytics on its source panel.
2. The GoodData project has been refreshed to pick up the change.

If either step is missing, the field exists in your project but doesn't show up in the data table you build reports from.

Where to check the analytics configuration

A field's analytics setting is at the panel level — Details, Rollup, Grand Total, PO, Actuals — depending on where the field lives. The toggle is typically labeled something like Use for Analytics. Open the field's configuration in the source panel and confirm the setting is on.

![SCREENSHOT NEEDED: Field configuration showing "Use for Analytics" toggle]

If the field works in another project but not this one

The fastest check is to compare the field setup between the two projects side by side. Two things specifically:

• The Use for Analytics (or equivalent) checkbox is set the same way.
• The field ID (technical name) is identical. GoodData keys off the technical ID, not the display label — two fields labeled "GL Accounts for Opex" with different technical IDs are different attributes in GoodData.

When a GoodData project refresh is needed

Even when the analytics setting is correct, the GoodData project may not have been refreshed since the change. A standard nightly refresh usually picks it up. If your team needs the new attribute immediately, or the nightly hasn't caught up, a manual sync may be required. Signs a manual refresh is needed:

• You turned on Use for Analytics for the field today and it's still missing the next morning.
• A data-model change accompanies the field (a new column or dataset).
• The attribute appears but its values are empty.

What to do

1. Verify the field has analytics enabled on the correct source panel.
2. If you have a working comparison project, confirm the field IDs match.
3. Contact Support and tell us which project, which field, and whether you've already verified the analytics setting. We can confirm the GoodData project version and trigger a manual refresh if needed.

Related articles

• The GoodData data table — what attributes are available
• The Insights tab — overview and navigation
• Master Settings → Analytics/Insights
• Multi-currency reporting — enabling and currency filters