Getting incorrect result while computing an output using Beast mode

Hi,
The below beast mode works perfectly when only 'metric A' is selected as a filter.
However, when 'metric A' and 'metric B' is selected as filter under 'metrics' then the resulting value changes.
Note: I have attached a screenshot when the correct value is coming with only metric A as 72224, whch changes to 72213 with 2 metrics in filter.
(case when `metrics`='metric A' then (case when ((`values` - lag(`values`,1) OVER (ORDER BY `date_id`))=0 and `date_id`>'2022-10-01' ) then (((lag(`values`,1) OVER (ORDER BY `date_id`)) - (lag(`values`,7) OVER (ORDER BY `date_id`)))/7 + `values`) else `values` END ) end)
Answers
-
When you’re filtering and including a and b your lag function will pull data from metric a and b. You’ll want to add PARTITION BY ` metric ` to your lag statements to make sure you’re not jumping metrics with the lag
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 -
@GrantSmith Thanks for the solution, this works. However, now when I proceed with the changes over the bar chart, the width size reduces. Attached old vs new case. How can I get the increase the bar width size?
0 -
There is another issue arring here of the duplicate dates on X axis. How can I overcome this issue?
0
Categories
- 10.5K All Categories
- 3 Connect
- 913 Connectors
- 250 Workbench
- 458 Transform
- 1.7K Magic ETL
- 69 SQL DataFlows
- 476 Datasets
- 183 Visualize
- 249 Beast Mode
- 2.1K Charting
- 11 Variables
- 16 Automate
- 354 APIs & Domo Developer
- 88 Apps
- 3 Workflows
- 20 Predict
- 5 Jupyter Workspaces
- 15 R & Python Tiles
- 245 Distribute
- 62 Domo Everywhere
- 242 Scheduled Reports
- 20 Manage
- 41 Governance & Security
- 168 Product Ideas
- 1.2K Ideas Exchange
- 9 Community Forums
- 27 Getting Started
- 14 Community Member Introductions
- 55 Community News
- 4.5K Archive