Filip Charikov
03/06/2024, 3:23 PMRUNSUM(COUNT())
) based on 2 dates. When I do this runsum MAQL statement, it breaks because RUNSUM can only accept 1 date.Joseph Heun
03/06/2024, 4:18 PMFilip Charikov
03/06/2024, 4:48 PMFilip Charikov
03/06/2024, 4:49 PMJan Soubusta
03/06/2024, 7:08 PMSELECT (
SELECT COUNT({label/commit_id}) BY {label/created_at.day} ALL OTHER
) / (
SELECT COUNT({label/commit_id}) BY {label/updated_at.day} ALL OTHER
)
If I slice it by created date, it "works", see screenshot.
1. It does not use RUNSUM, but it should be possible to extend it accordingly
2. It slices by created date. Not 100% sure if it is what you need, but generally I don't see other way how to calculate something meaningfulJan Soubusta
03/06/2024, 7:15 PMJan Soubusta
03/06/2024, 7:20 PMJan Soubusta
03/06/2024, 7:22 PMMultiple contexts for count, attribute='attribute/commit_id/cicd_demo_production'
Jakub Sterba
03/06/2024, 7:34 PMJakub Sterba
03/06/2024, 7:36 PMFilip Charikov
03/06/2024, 7:36 PMJakub Sterba
03/06/2024, 7:42 PMFilip Charikov
03/06/2024, 8:53 PMSELECT RUNSUM(SELECT COUNT({label/gooddata_main_data.claim_id})
where {label/open_claim_status_map.open_claim_status} = "Missing or Incorrect Info"
OR {label/open_claim_status_map.open_claim_status} = "No Claim on File"
OR {label/open_claim_status_map.open_claim_status} = "Processing")
FOR EACH {label/open_claim_status_days_since_submission}
Jakub Sterba
03/06/2024, 9:32 PMselect {metric/count_metric} where {label/days_since_submission} in ("1")
column2: select {metric/m} where {label/days_since_submission} in ("1","2")
column3: select {metric/m} where {label/days_since_submission} in ("1","2","3")
...
The titles of columns for metric or attribute title in rows can be renamed on level of insight so you can display just numbers in table header on top (1,2,3…) instead of names of metrics.