MarkSnodgrass Coach

You can do this by using Magic ETL. Use the Rank & Window tile and Rank your scores. Add a Group By tile to get a Count of the total rows in your dataset. Join it back to the Rank & Window tile so that the total row count is now a column next to every rank. You can then do the math in the ETL or in a Beast mode to…

@imelendez if the rows are exactly the same, does it matter which one it keeps? If there is another column that is a date entered type column, then the rows would become unique and then both would be kept. If you have rows that are the same and the only difference is a date entered type column, you could use the group by…

Since you are using append in your connector, you can create a Magic ETL to give you the unique rows you are looking for. You can use the Remove Duplicates tile in Magic ETL to give you a distinct list of rows. https://domohelp.domo.com/hc/en-us/articles/360043427373-Magic-ETL-Tiles-Edit-Data#3. Another approach, but more…

Based on your screenshot, your dataset is doubling because you are sending the entire dataset to Value Mapper 2 and the entire dataset to Value Mapper 9. In order to avoid the duplication, move your Value Mapper 9 and and Set Column Type 2 to be after Set Column Type 9 so that your source data is not being split out. Also,…

You can mimic the date range quarter display by using CONCAT in a beast mode like this: CONCAT(YEAR(`dt`),'-Q',QUARTER(`dt`)) If this is applied to all your datasets, then this should work as a shared filter. The other option would be to use the date field that is driving your date range as your shared filter and use the…

That is currently not possible. You might want to try submitting this as in the ideas exchange and see if it is something that can be added in the future.

You may want to consider using the tags feature to manage your datasets. You can select multiple tags in the search filter.

Have you tried using a pivot table card and putting the Item Status 1-4 in your row field, your date field in the columns field and then your Item Status field in the values field and choose the aggregation type of Count? Based on your Excel screenshot, that should work. If this doesn't work, if you can provide what your…

@swagner you can use the MOD function to see if there is a remainder when dividing by 2 to determine if it is an odd or even number: CASE WHEN MOD(YEAR(`Order Date`),2) = 0 THEN 'Even' ELSE 'Odd' END

@user048760 Yes, using SUM would change the sorting. Click on the pencil icon to edit the sorting criteria and choose No Aggregation. That should fix your issue.

That's interesting Domo chose those colors as they are usually pretty color conscious. I don't see anything in their documentation that allows you to change which colors are being used. A couple of ideas for you: Submit this issue in the Ideas Exchange section of the Dojo to allow for this customization or have them select…

Do you have any other fields in your Sorting properties? Or is the dayofweek beast mode field the only field that is in the Sorting properties?

You can use the Dataset Copy connector to copy a dataset from one instance to another. It can be scheduled just like any other connector and would allow your subscribers to build dataflows off of it. Here are instructions on how to set it up.…

That's a pretty large case statement. I would suggest create a lookup table in a web form or Excel file and then join it to your main dataset in a Magic ETL dataflow. This will process much faster and be easier to maintain.

You might try the Heat Map chart. It is useful for things like this. See the example in this KB article: https://domohelp.domo.com/hc/en-us/articles/360042924634-Heat-Map

You can use the GETDATE() function to generate the current date and time in Microsoft's SQL SELECT GETDATE() AS Batch_Last_Run FROM tablename If you are using MySQL, you would use CURRENT_TIMESTAMP SELECT CURRENT_TIMESTAMP() AS Batch_Last_Run FROM tablename

If you have never built a card before, I would watch this Domo video that walks you through it. I would also spend some time to watch the other videos in the help center to help you better understand how to make use of Domo.

By default, scheduled reports have a start and end date. I would check to see if the end date has passed, which would be why they no longer receive it. If that isn't the case, I would add yourself to the scheduled report and see if you get it as well as an e-mail address of a non-Domo user (like a personal e-mail address)…

I would create a beast mode and divide that number by 1000. Then drag that field into your axis and use the title or description or some other area to let the user know it is in the thousands.

@user091100 glad it worked for you. If you can mark the answer as accepted, that will help other people in the community.

Try this: Use the DATE() function to extract the date from the field you want just the date Use the TIME() function to extract the time from the field you want just the time Use the ADDTIME() function to add the two together ADDTIME('dt','tm') I did a quick test in Magic ETL and it worked for me. I had them each separated…

Check your chart properties and data label settings and see if Use Scale Abbreviation is checked. That could be causing it. You can also click on Reset Chart Properties and that should fix it because, by default, the individual values are not abbreviated.

It looks as though that Domo feature is deprecated. I would look at the main Domo Developer page to read up on how to create a custom app. https://developer.domo.com/

You can create a beast mode that looks like this: CASE WHEN 'Scheduled Shift' = 'Shift' THEN 'Same' ELSE 'Different' END

You can create a beast mode to calculate the first day of the week with this: DATE_SUB(`dt`, INTERVAL (DAYOFWEEK(`dt`) - 1) DAY) You would then drag this field into your table and then change your date filter to group by none. @GrantSmith did a nice write up about this and other date functions here in case you want to dig…

Haha @GrantSmith !!! 😂

Yes, I have found that joins (at least in Magic ETL) are case sensitive. You can use the Formula tile (if you have Magic ETL 2.0) or the Text Formatting tile (if you have Magice ETL 1.0) and use the UPPER function to convert everything to uppercase prior to joining.

If your employee report dataset contains employee title then I would take that dataset and then bring into Magic ETL and use then join it to your goals dataset that contains employee title, frequency (day, week, visit), and goal number (3, 5, 9, etc.). I would then use multiple filter tiles to separate them, one for each…

It seems like you might need to reach out to Domo Support who will transfer the ticket to connector support and they may have some insight. Did you try installing the Quickstart app to see if one of the cards created is getting the data you want and it is not labeled something very intuitively?…

Completely agree with this idea. This limitation is very frustrating.