Remove the filter turnover >0, the result is 3081, however it should be 280 since we have a bus_date in this table, and not only new players active in this period but also the exist ones.

Thinking completed I'm sorry, but the provided knowledge sources do not contain enough specific information about your exact data model, metric definitions, or table structure to fully resolve why removing the

turnover > 0

filter produces 3081 instead of 280. However, based on how GoodData evaluates metrics and filters, here are key areas to inspect: 1. Date Dimension Mapping: If you have multiple date dimensions (e.g., a player's initial registration/creation date vs. an activity

bus_date

), ensure the date filter applied to the visualization or dashboard is explicitly connected to

bus_date

. If it is scoping by another date or evaluating over "All time", existing players will not be restricted to the active period [Date filters; Time-over-Time]. 2. Distinct Counting across Activity: When removing

turnover > 0

, the metric might count all player records present in dimension or master tables rather than those with actual activity on

bus_date

. If you are counting players: ◦ Make sure your metric counts distinct player identifiers (e.g.,

SELECT COUNT({attribute/player_id})

) from the activity fact dataset where

bus_date

exists [COUNT aggregation]. ◦ Check if an activity condition is still necessary (for instance, ensuring an activity fact record exists or

WHERE {fact/turnover} IS NOT NULL

). Resolving the specifics of your data model and calculation requires inspection by a GoodData Support team member. The Support team monitors this Slack community and will step into the thread as needed. To help the Support team investigate, please add the following details to this thread: • The exact MAQL definitions for the metric(s) involved. • The visualization setup (attributes in rows/columns, filters applied). • The affected workspace ID and dashboard/insight URL. • A brief description of how

bus_date

and player entities relate in your Logical Data Model (LDM). Support Options • Community support (Startup & Professional): You are already in the right place. The GoodData Support team monitors this Slack and a team member will join the conversation when human review is needed, so please keep the discussion and post the requested details directly in this thread. You can also consult the Community Forums. • 24/7 Support (Enterprise plans): If your account tier includes 24/7 Support, or if you are experiencing a Severity 1 (L1) critical issue, these direct options are available in addition to this thread: ◦ Submit a ticket: GoodData Support Portal ◦ Email:

support@gooddata.com

◦ Phone: +1 (415) 200-0194 👍 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.

31. Player Summary - GoodData Cloud the result shows the number of all players active in last month, not the new players in this period.