RobSomers Coach

@Jones01 That looks like a spark line chart. https://domohelp.domo.com/hc/en-us/articles/360043429353-Spark-Line-Chart

@gbrown You'll want to use an ETL with the Rank & Window tile to create a 'Current Status' column. You'll want to do use RowNumber and order on Timestamp in descending order, and then partition by part number (and owner if a part number can have multiple owners at the same time). This will give the row with the latest time…

@Jones01 In your ETL, you'll probably want to create a formula to calculate the fiscal year (could also do this in a beast mode depending on use case). You would just write a formula like this for each year that you need: case when 'date' >= '2022-03-01' and 'date' < '2023-03-01' then 2022 when 'date' >= '2021-03-01' and…

@ST_-Superman-_ I didn't think there was but thought I'd double check. Thanks for the confirmation!

@Jackie96 I think you could also use the FIXED function to achieve what you're after: https://domohelp.domo.com/hc/en-us/articles/4408174643607-Beast-Mode-FIXED-Functions

@cbreen You'll want to modify it to the following: case when month(`date_purchased`) = 8 and DAYOFMONTH(`date_purchased`) >= 11 then ( case when month(`date_purchased`) = 10 and DAYOFMONTH(`date_purchased`) <= 10 then 1 else 0) else 0 end This will say if the date is after 8/11 then look at if it's before 10/10 and if it…

@NateBI In the data label for each value field, you can put <br> and it won't remove it but it will make it blank.

@Kunal I agree with @MichelleH. If you aren't doing any aggregation on the account balance, then it won't group and aggregate that field and it will just graph each line separately.

@Kunal It will be an issue of sorting on your card, nothing in the ETL most likely. And I think the issue will probably be that in your card you need to sort by whatever date you're graphing by.

Do you mind posting a screenshot of your sorts?

@Kunal Are you sorting on any fields? That can sometimes cause this issue, so I would recommend removing any fields you're using to sort and see if there's one that's causing the problem.

@Jones01 Having two columns named the same would create a problem. When they're imported into Domo, your query has p.zone_id and s.zone_id. But when the data gets imported, since the p and the s are only used to identify which zone_id is which within your query, the column names are actually just zone_id and zone_id. Since…

@Jones01 Are you doing the join in an ETL, a dataset view, or prior to importing into Domo?

@Morgan This depends on what you have available in your datasets. If both datasets have a username or some other id column that can be used to identify who the user is, you can use an ETL to do left join between the Tickets table and the Users table. This will then look through your ticket table and attach user record from…

@jrtomici The Remove Duplicates tile should let you select multiple columns, so you would select the ID and Num columns to look for duplicates and in your example it would see row 2 and 3 as duplicates, and then the ETL would remove one of them and you would just be left with one row with ID of 1 and Num of 4. It would…

@jrtomici You can use the Remove Duplicates tile when creating an ETL if it doesn't matter which row you keep:…

@GabrielaCortes I'm guessing that the blank cells are actually null. You'll need to modify you're column A. Use the function: IFNULL('Column A',' ') This will replace nulls with blanks and you can do your filtering using this and it should work how you want it to with blanks.

@GabrielaCortes If I understand correctly, you want the filter to identify rows where column A is not false and column B is false. You'll want to create a beast mode like the following: case when 'Column A' <> 'False' and 'Column B' = 'False' then 'Include' else 'Exclude' end

@Travis I don't believe there's a way to add hover text to legends. There could be a way of doing it with DDX bricks but there's nothing for normal cards. You could include the different definitions in the card description.

@pstrauss There a couple of options for handling different columns. Here's an article on appending and differing rows: https://domohelp.domo.com/hc/en-us/articles/360044876194-Magic-ETL-Tiles-Combine-Data#:~:text=The%20Append%20Rows%20tile%20lets,data%20structure%20and%20data%20type. The best way to guarantee that…

@pstrauss If you just have single charts for each interaction (Emails, Chats, Phone Calls, etc.) then you can just graph by the interaction specific data. If you want everything to function off of a single date (all Emails, Chats, and Phone Calls for Jun 2022), then you'll have to stack your data. Instead of joining, you…

@WorldWarHulk I think I answered the current quarter question in your post you created a little bit ago: https://dojo.domo.com/main/discussion/55584/how-to-capture-the-current-quarter-using-beastmode#latest For combining that with your current beast mode, I think the following should work: case when…

You could do this: case when QUARTER('Date')=QUARTER(Curdate()) and YEAR('Date')=YEAR(Curdate()) then 'True' else 'False' end

Welcome!

I actually think a better and easier way to do this would be using the FIXED function. You can do this either using a formula tile or using a beast mode in a card. The formula will be like this: AVG(AVG('Time between purchase')FIXED()) I don't think the FIXED function will show up in the list of formulas in the ETL, but it…

@SGPA You could also create a another date column using a formula that is the previous year (ex: Jan/22 would have Jan/21 in the new column) and then join the table on itself using the original date column and the previous year column and just rename the AVG YTD column from the previous year join to AVG YTD Previous Year.

If you want to do this just using views, then I think @Jones01 has the right idea. Depending on how many joins you want to do, this might get just as complex as just using an ETL. You could try doing this using a SQL dataflow as that might provide you with a little more familiarity with the process, but depending on the…

You won't need your group by tile, just the Rank & Window tile.

@sarahi6 Are you wanting for each line to have the average time between purchases for all customers? If so, you'll want to use a Rank & Window tile to do that. https://domohelp.domo.com/hc/en-us/articles/360042922814-Old-Magic-ETL-Tiles-Rank-and-Window

@crico For your QM Metrics Date Filter, when you added it to the page, did you click on the arrow next to it? This lets you select the datasets that it should be applied to, so you could check all the datasets used on the page.