While working on a Constellation view, I ran into an interesting behavior around Data Pages, Associations, and the Allow query option.
At first, it looked confusing, but once understood, it made complete sense.
-----The scenario------
I needed to display:
Fields coming from an associated data type
A calculated value prepared from the data page results
All of this was to be shown in the UI.
What I observed:
When Allow query is not enabled:
->The association column does not appear in the view
When Allow query is enabled:
->The calculated value (prepared via logic) does not display
So enabling Allow query solved one problem, but introduced another.
Why this happens (in simple terms):
->Allow query exposes raw data directly for querying in the view
Association fields rely on this query capability to appear
->Calculated or derived values, however, are meant to be prepared before the UI
Mixing both patterns leads to inconsistent UI behavior
How I solved it:
Instead of relying on Allow query:
->I created a separate field to hold the associated value
->Populated it through the Data Page Response Data Transform
->Disabled the Allow query option
->Used only prepared, display-ready fields in the view
This allowed:
Association data to display correctly
Calculated values to appear consistently
Cleaner separation between data preparation and UI rendering
My Learnings:
->Allow query is useful, but not for every scenario
->Association fields and calculated values don’t always work well together when queried directly
Preparing data in the Response DT gives more control and predictable UI behavior.
Understanding this helped me design cleaner and more reliable Constellation views.
Sharing this in case it helps someone facing similar association and display challenges. Feel free to share your thoughts 
If the video cannot be accessed here, kindly refer the below link!