Good Morning - I have a query regarding seperate date tables and utilising them within metrics which are not linked in the model. I have a table called jobs which has a complete status date field - a common metric would be to look at count of jobs per month. I have an unrelated table which is a row for each day between 2 years ago and 2 years ahead which shows if the day was a "Working Day". The end outcome would be to be able to show in a table initially but within visuals would be month (complete status), count of jobs, working days in month, avg jobs per working day. But with there being no link between the jobs dataset and the dates dateset this is proving difficult.

Good morning! Your scenario—wanting to combine metrics from two unrelated tables (Jobs and a Working Days calendar) in a single visualization—is a common challenge when the datasets are not linked in the Logical Data Model (LDM). Key Points from the Knowledge Sources: 1. Unrelated Datasets in LDM: GoodData metrics and visualizations rely on relationships defined in the LDM. If your Jobs table and Working Days table are not connected, you cannot natively aggregate or display their data together in a single insight, such as "jobs per working day per month," because there is no join path between them. This is confirmed in several community discussions, where users faced similar issues and were advised that, without a model relationship, combining such data is not directly supported in GoodData metrics or visualizations [[Community Slack Example](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1752587554236339?thread_ts=1752587554.236339&cid=C04S1MSLEAW)]. 2. Possible Workarounds: - Pre-join in the Source: The most robust solution is to create a relationship between the two tables in your data source or ETL process, so that the Working Days table can be linked to the Jobs table via the complete status date. This would allow you to aggregate jobs by working day/month. - Model Change: Add a reference from the Jobs dataset to the Working Days dataset in your LDM, mapping the complete status date to the date in the Working Days table. This would enable you to slice jobs by working day attributes. - Separate Metrics: You can create separate metrics for "count of jobs per month" and "working days per month," but you will not be able to calculate "avg jobs per working day" in a single metric or visualization unless the datasets are related [[Community Slack Example](https://gooddataconnect.slack.com/archives/C04S1MSLEAW/p1752587554236339?thread_ts=1752587554.236339&cid=C04S1MSLEAW)]. 3. No Native Cross-Join: There is no built-in feature in GoodData Cloud to cross-join unrelated datasets in a metric or visualization. Attempts to do so will result in incomplete or misleading results, as the platform cannot align the data without a defined relationship. Summary: To achieve your desired outcome (month, count of jobs, working days in month, avg jobs per working day), you will need to establish a relationship between the Jobs and Working Days datasets in your LDM. Without this, GoodData cannot natively combine the data as you described. If you need further guidance on how to adjust your LDM or ETL process to support this, please let me know!