hi, why is my filter here only showing 4 values, b...
# gooddata-cloud
s
hi, why is my filter here only showing 4 values, but when I group by the same column, it's sh0owing all of the statuses correctly? @Mauricio Cabezas @Moises Morales
m
Hi Sasha, my guess is that the values are being excluded due to the connections of the corresponding datasets in your LDM. An easy way to check what is happening behind the scenes is by saving the insight and change the "edit" in the URL to "debug", this will allow you to get the explain zip file of the insight including among other files the SQL query sent to your database. I recommend reviewing the query logic and adjusting your LDM accordingly so the insight behaves accordingly.
s
this is inside of an embedded view
@Moises Morales @Mauricio Cabezas the status includes
Copy code
and a."STATUS" in (
    'STARTED',
    'SUBMITTED',
    'APPROVED',
    'RESIDENT',
    'WAITLIST',
    'REJECTED',
    'CANCELLED',
    'ARCHIVED'
  )) AS "__sql_4370d07e11787cbe945c7073b1adb97d") AS "__sql_4370d07e11787cbe945c7073b1adb97d"
all the values are present in the sql query
and yet this is still what I see
j
Hi Sasha, Can you please DM us direct URL into the Report in question? Thanks
s
dm'ed @Julius Kos
m
The issue here is similar to the one reported here: https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1744622370551589. The values in "Application Status" are filtered out by the condition fp."STATUS" = 'SUCCESS that corresponds to "FEEPAYMENT.STATUS = 'SUCCESS'" from the "Fee Payment" table. The table "Application" is connected to it via a M:N connection, but the condition is integrated to the query in the backend even if the attributes do not travel across the M:N connection. As mentioned in the linked thread, the issue can be addressed by changing the connection to 1:N, adding the missing status to "FEEPAYMENT.STATUS = 'SUCCESS'" if it makes sense, or more conveniently, include a metric to the insight. Note that including a metric, will force the values to appear, but the filter will still only show the 4 original values. Our engineers are aware of this bug and I have submitted an internal ticket to look into it. My apologies for any confusion or frustration this may have created.