Hi Anjali,
Thank you for explaining it. The issue stems from how datasets are connected.
A measure (like Award Amount from Awards) can only be sliced/filtered by attributes that are in the same dataset or that have an oriented path to that dataset following the direction of the arrows. If no oriented path exists from Intake to Awards, attributes from Intake (e.g., Intake Status) become incompatible and the measure gets hidden in Analyze.
This is why adding Intake Status hides Award Amount—there’s no valid (arrow-direction) path connecting Intake to Awards in your model. GoodData hides incompatible items and filters to prevent invalid queries.
You can fix it by ensuring a 1:N relationship path exists from Intake to Awards in the arrow direction that reaches the Awards dataset (e.g., Intake -> Applicant -> Awards), or connect Awards so that its path points back toward Intake. Create relationships in the LDM Modeler using the originating-to-target arrow and foreign key selection.
If the business logic is many-to-many (e.g., a bridge between Applicant/Intake and Awards), consider an M:N setup (bridge dataset) so measures in Awards can be sliced by attributes across the model; otherwise, they’ll stay limited by one-to-many reachability.
I will here attach some documentation that might be useful to you.
Model Data
Reading the Model
Rules of data modelling
Common Pitfalls
Create relationship between datasets
Many to Many relationship
Thank you.