MichelleH Coach

@user028582 Here is a knowledge base article that shows how to use the Rank & Window tile and Group by in Magic ETL: https://domo-support.domo.com/s/article/360044876094?language=en_US Either method will get you what you need, so let us know which one you want to try and we can help answer any other questions.

@user028582 Rather than using a formula, I'd recommending using a Row Number function in the Rank & Window tile to identify the last batch (order by last batch date, descending). Then you can use a filter tile to only include data where the row number = 1.

@faisalnjit That's correct. If you need to make changes, then your colleague who created the account must do it. Otherwise you would have to create a new account yourself and transition all existing datasets to the new account. In general I recommend creating a dedicated "Account Owner" user to own all dataset accounts.

@Stuck Of the options you're testing, SUM(IFNULL(`value measure`,0)) should give you the best result. The reason your case statement didn't work is because you had aggregate functions inside the case statement, which can cause sorting issues. Whenever you need to use an aggregate and a case in the same function, it's best…

@Stuck To clarify, by "non-valued" do you mean the the value is zero, null, or an empty string? Regardless, you can get around this by hard-coding a value using a CASE or IFNULL function. That's probably not the answer you're looking for, but this is by far the simplest way to accomplish what you need. You can still…

@user02055 Just to be safe, try searching your job list screen for the name of the job to see if there are multiple. It may also be worth checking with any other Workbench users to see if they had any other jobs enabled.

@Ruban Can you please provide more information on what you are trying to accomplish so that we can better answer your question?

@user02055 Can you confirm that there are no other jobs enabled for this same dataset?

@chetan_cricut You would need to create a calculated field to concatenate the first and last day of the week (similar to how you created the week start date) for your x-axis, sorting by week start date. Your x-axis calculation would look something like this: concat(date_format(`Date` - dayofweek(`Date`) + 1,'%b %d), ' -…

@user02055 In that case it sounds like there is a problem with your workbench schedule or your database maintenance is taking longer than anticipated. What time do you usually get the error emails?

@Josh_Overett Your use case sounds like it's better suited for a Summary Number rather than Smart Text. Here are a few KB articles that can help guide you on out to display a date in the summary number using beast mode: https://domohelp.zendesk.com/hc/en-us/articles/360043428753-Configuring-Your-Chart-Summary-Number#5.

@user02055 You can turn off error emails by deselecting the "Notify on Error" checkbox in the Notifications tab on your Workbench job: https://domohelp.zendesk.com/hc/en-us/articles/4407013819671-Setting-Notifications-in-Workbench-5-1 However, I would recommend adjusting the schedule to start a little after 6 am to account…

@chetan_cricut If you would rather manage this at the card level, then add a week start date field to the x-axis and set the date graph by setting to "none".

@gbrown I second @kivlind's suggestion of using a date lookup table. Domo also has a Fiscal Calendar feature, which allows you to group card data by fiscal period: https://domohelp.zendesk.com/hc/en-us/articles/360042924254-Using-a-Fiscal-Calendar

Yes, it would be great to be able to manage this at the group level too so that the alerts can be tailored to the necessary audience

@Jack_Kaye I don't believe there's a simple way to do that, but here is what I'd recommend: Create a copy of the existing card using "Save As" In the copied card, add a drill layer to inherit all the configurations of the top level Re-add any necessary filters, then save the drill Open the top layer card in Analyzer and…

@jrtomici You can accomplish this by creating a variable with values for each type of calculation. Then you can create a beast mode based on which calculation type is selected in your variable control like the one below. This beast mode would then be used as the Value/Y-Axis in your card. case when `Calculation Type` =…

@Jack_Kaye You can change the source dataset for a drill path as long as all of the filter fields have the same name in both datasets. Once you add a drill layer to a card, you can change its data source by clicking on the dataset name in the "Data" section on the top left of Analyzer, then searching for the new dataset…

@NateBI You can change the text you see when there is no data in the card under Chart Properties > General > No Data Message

@Utz Are you writing this case statement in a Beast Mode or a dataflow? I've found that the syntax from your first formula works in SQL dataflows, but not in beast modes. In general, case statements work most consistently across different Domo engines using the syntax below: CASE WHEN `SeasonalDescription` = 'Easter' THEN…

@pstrand2 Yes, you would want to use the Card Fields with Beast Modes report from the Domo Governance Connector. This will tell you which cards use each field by dataset.

@Chris_Wolman You'll likely have more luck with this if you identify the max date in a dataflow instead of using a fixed function since you're trying to aggregate based on the result of another aggregation. If you create a dataset field called `Max Date` in your dataflow, then the beast mode would look like this: sum(case…

@user028582 I recommend adding the beast mode below as a sort field in your card to order all these times chronologically: HOUR(`EVENTTIME`)

@Stucker In that case, I'd recommend reaching out to your admin or Domo support if you're not able to save any beast modes at all.

@Stucker I don't see anything in the formula itself that would be causing an error. Does the error message appear when you try to save the beast mode or when you try to use it in the card? There may be something else in your card that is causing an issue.

@kathint303 Where are you manually typing the dates now? Is it in the date range or somewhere else in the analyzer?

Agreed. This would be especially helpful for reducing load time when building cards on large datasets.

@Le1331 Are you using the Formula Tile or a Group By tile? Aggregate functions like counts and sums must be done in the Group By tile since they depend on the values across multiple rows. The Formula Tile only evaluates functions based on values within the same row.

@jaymin_63 Are you using HTML to add hyperlinks to your table? If so, you can include "target=_blank" after the URL to open the second dashboard in a new tab so you don't have to navigate away from the first dashboard to begin with. See the "Adding Links and Anchor Tags to Tables" section of this article for an example:…

@ALee I suggest checking out the Domo Governance Connector. There is a report on that connector called "Cards and Datasets" that includes the information you're looking for, along with the dataset for each card. You can export that dataset to CSV or Excel to audit what cards are on each page.