MarkSnodgrass Coach

@Ashleigh is a veteran user of CourseBuilder. She may be able to help you.

If you go to the ETL and then click on Versions, you should be able to restore to a previous version where the output dataset existed. https://domo-support.domo.com/s/article/360042923074?language=en_US

You can use the group by tile to sum your quantity by invoice number and then join it back to your original dataset to get the total next to the individual items by joining back on invoice number. Your ETL would look something like this:

@zuchu you are going to need to replace the "date" column with the name of your column that is in your dataset. Also, which card are you using? That may affect if this solution will work for you or not.

You can create a beast mode that you would add to your filters to filter out weekends from your dataset. Your beast mode would look like this: CASE WHEN DAYNAME(`date`) IN ('Sunday','Saturday') THEN 'Exclude' ELSE 'Include' END You would then add this to your filter and filter to Include.

@mlb I believe it lets you choose a date in the date range field when there is no date field added to the list of columns in the table. Once you add a date field to the table, the option to select a field in the date range is greyed out. It is odd behavior and would be worth submitting as an enhancement in the ideas…

@jrtomici I did something similar where I break up words into individual values and then put them on each row. I walk through how to do it in this video. Hopefully this will help you.

That seems like a bug for both of you. I can click on the 3 dots on dataset fields on datasets that I don't own.

@MichelleH and @NathanDorsch I'm curious... in the main data center area, do you have the ability to click on the 3 dots and add additional tags or remove tags on the actual datasets and dataflows themselves? Or is that not there as well?

Very strange. I tested in another instance and I didn't have the issue you are having. Unfortunately, I think you may have to log a support ticket and have them determine what the issue is.

It's worth a test on a dataset you own. I am an admin in my instance, so I can't replicate your issue. @MichelleH and @NathanDorsch are you both non-admins?

Odd... do you have custom roles enabled and possibly don't have the ability to delete tags?

Did you click on the 3 dots next to the existing tag and then choose Add a Tag? You can then remove existing tags in the place where you add tags by clicking on the x next to the tag.

@AndreiA I would try using the str_to_hex function on your id field in the formula tile and then build the rank off of that. This will allow the rank to see those two values as different values rather than the same.

There are a lot of ways to group data in Domo. In your case, I would suggest using the pivot table card to have the months as columns. Here's the KB article that would help you learn how to set it up. https://domo-support.domo.com/s/article/360043429473?language=en_US Hope this helps

@froghunter I did something similar where I am looking at a sentence and breaking it up into individual words and don't know how many spaces are in each sentence. This video walks you through how to do it. You would need to look for \\ instead of spaces in my example. You will also need to do a group by at the end of your…

Those period-over-period cards are kind of different in how they function. I believe your summary number isn't working as you want because your date range filter is set to this year. That keeps anything that would be in the denominator portion of your formula from being counted since that is looking for the previous year.…

@damen what is your date range filter set to? do you have any other filters in place?

Try doing this as a different way to count without using the count aggregation inside the sum aggregation. SUM(CASE WHEN YEAR(`time_stamp`) = YEAR(CURRENT_DATE()) THEN 1 ELSE 0 END) / SUM(CASE WHEN YEAR(`time_stamp`) = YEAR(CURRENT_DATE())-1 THEN 1 ELSE 0 END)

I feel like it is a bug that it does this and could be worth reporting to Domo. The workaround I have found is that Domo will use the last date field added to your table card as the date range field. So, if the field that you want to use as your date range is not being used, remove it from your table card and then add it…

You can create a beast mode that looks like this: CASE when `datefield` >= CURRENT_DATE() AND `datefield` <= LAST_DAY(CURRENT_DATE()) THEN 'Yes' ELSE 'No' END This should work for you.

For the OR statement, you need to restate the field you are comparing against like this: WHEN `ComplaintDesc` LIKE '%ICE%' OR `ComplaintDesc` LIKE '% ICE%' THEN 'ICE'

Depending on what other date fields are in your mega table, you can also use the date range filter and switch the graph by to month and it will format the date fields automatically for you. It depends on what look you are going for if that option would work for you. Just wanted to make sure you are aware of that option.

I often use the LAST_DAY() function to group dates by month and year. It will move all the dates in the month to the last day of the month so then it becomes easier to aggregate.

@Pello the period over period charts are pretty limited in customizing, and you can't customize the legend labels. I would suggest using the line+bar chart and using the beast mode formulas to create your custom series names that would be used in the legend. I created a video that may help you.

@SaloniShah A couple things to point out here: Your x-axis is not being recognized as a date field. When it isn't a date field, Domo will not let you use the "graph by" option in the date range filter. I see your x-axis field is "created date", but your formula in your ETL screenshot is creating a field called…

In your Data Label Settings, set Show Datalabels On to Lines Only.

You can keep your y-axis as count, but change your chart type to the 100% stacked bar. It is found under the vertical bar chart type. This will get your items to add up to a 100%.

Agree with @damen that there is not a perfect solution since you have to assume a single first name and single last name, but here are some things you can do to get close if you can't fix the source data. Leveraging the formula tile in Magic ETL, you can create formula fields and then reference within that same tile. Here…

You could utilize the unix_timestamp function which will convert your timestamp columns into the number of seconds since 1970. This will make both fields integers, so you can do basic math to subtract the two to find the number of seconds and then divide by 60 to get the number of minutes. You can then use that number…