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
- All Categories
- 1.2K Product Ideas
- 1.2K Ideas Exchange
- 1.4K Connect
- 1.1K Connectors
- 273 Workbench
- 2 Cloud Amplifier
- 3 Federated
- 2.7K Transform
- 78 SQL DataFlows
- 526 Datasets
- 2.1K Magic ETL
- 2.9K Visualize
- 2.2K Charting
- 440 Beast Mode
- 23 Variables
- 514 Automate
- 115 Apps
- 391 APIs & Domo Developer
- 8 Workflows
- 26 Predict
- 10 Jupyter Workspaces
- 16 R & Python Tiles
- 332 Distribute
- 77 Domo Everywhere
- 255 Scheduled Reports
- 67 Manage
- 67 Governance & Security
- 1 Product Release Questions
- Community Forums
- 40 Getting Started
- 26 Community Member Introductions
- 68 Community Announcements
- 4.8K Archive