MarkSnodgrass Coach

Comments

  • Since Zulu time is the same as UTC and Domo is expecting the datetime to not have a timezone label at the end, I would either use the LEFT function to get only the datetime data, or use the REPLACE function to remove the Z from your string and then Domo will interpret it as a datetime value. REPLACE('datefield','Z','')
  • I might be able to make better recommendations if you provided a sample of your data, but it is likely giving an error because of the quotes around 1 after your greater than or equal to. Try this for starters: (CASE WHEN (COUNT(DISTINCT `ReportDate`)) >= 1 and (COUNT(DISTINCT `Agents`)) >= 1 THEN '1' ELSE ? END)
  • @dacorson I have had the same experience myself when converting Redshift dataflows to Magic ETL and have had to be very mindful of my naming conventions because Analyzer is case sensitive. It would be a nice enhancement if Analyzer did not care what case a field was when you changed datasets. I would recommend submitting…
  • The period over period chart expects a single date column, so you are going to want to restructure your data, or look at a different chart. If you restructured your data like this: Machine Name DateLastSync PC1 7/1/2021 PC1 6/1/2021 PC2 6/1/2021 The period over period chart could work for you.
  • That is the correct way to do it. Sometimes, there is a delay in the output dataset seeing the new column order. Try refreshing your browser when looking at the data. You might also try adding an additional column temporarily in your select columns tile and verify that the output dataset display is seeing it.
  • @moneyshot Divergent colors were added as a chart property to heat maps a couple months ago. If you select that, it will default to red to green for the divergent colors. There are several additional properties within the divergent section to give you more flexibility. You can read about them in the Heat Map KB article.…
  • You can do this by creating a beast mode that would rename your fields and then drag that field into your series. Your beast mode would look something like this: CASE WHEN 'fieldname' = '{"Mode":"Auto","Rule";"Tree"}' THEN 'Point - Tree - Batch' WHEN 'fieldname' = '{"Mode":"Manual","Rule";"Tree"}' THEN 'Point - Tree -…
  • @eriena The screenshot that you provided is just a condensed list of connector, which you can get to by click on Connectors from the data center, just to the left of File. You can then type in the name of the specific connector that you want to use. I imagine, Domo will fix the "more upload methods" eventually, and you…
  • One easy way in the Add Formula tile is to multiply the column by 1 like this: "count"*1 I have used this multiple time to get a number to integer that didn't start out that way. If you aren't doing any data cleansing along the way, you can also click on the input dataset and change the data type for that column. (This…
  • @eriena I am getting the same thing in my instance. However, I never have to click on "more upload methods" to upload my Excel file. I just drag and drop it into where it says "drag and drop file" or click on the browse link just below that and navigate to where my file is. I noticed some recent changes they did to the…
  • If you are doing this in a beast mode, you can use INSTR and SUBSTRING to get it. It would like like this CASE WHEN INSTR(`column`,'876') > 0 THEN SUBSTRING(`column`,INSTR(`column`,'876'),7) WHEN INSTR(`column`,'877') > 0 THEN SUBSTRING(`column`,INSTR(`column`,'877'),7) END
  • @dacorson given that Domo just did a big release on the 14th. My guess is that something got messed up in your instance that is causing the issue. If you want to post the syntax for the window function beast mode that is in use when you try and save the card, we might be able to reproduce in our instances and see if the…
  • I just created a few earlier today and the card saved without issue. It does sounds like a bug and you might have to wait until support gets back to you. You might also try creating a new card from scratch and see if the issue still occurs.
  • Yes, you can do this very easily in Magic ETL using the Split Columns tile. Just drag the Split Columns tile in, select that column you wish to split, choose Whitespace for what to split on, place a check next to "keep extra splits", then give a name to the column that will hold the values before the space, click add…
  • @ntadesse Sorry, I don't have personal experience with using that connector, I just know it is there. It might be worth asking your CSM if they have anything they can provide because I don't see anything else in the KB beyond what I provided you.
  • You would need to use the Amazon Redshift Writeback Connector. Here is the KB Article about it: https://domohelp.domo.com/hc/en-us/articles/360043436893-Amazon-Redshift-Writeback-Connector
  • You can also use the Lookup Table feature under Transformations to join and then filter the information. https://domohelp.domo.com/hc/en-us/articles/360043437193-Combining-DataSets-in-Workbench-5 You might also consider doing this work in Domo in Magic ETL. It would reduce the workload on your system and you can leverage…
  • You don't have to write standard SELECT statements in the query window. You can execute stored procedures in the query window, which seems like what you might want to construct to allow for the dynamic nature that you are looking for. You can also write queries against views in case that would work for you.
  • @jaeW_at_Onyx I did notice an error in my statement. I should be subtracting 17 hours to get to 7am of the previous day and not 7 hours. If today's date is 7/13/2021, then SUBTIME will yield 7/12/2021 07:00:00 and ADDTIME will yield 7/13/2021 07:00:00. This would do the trick in my opinion. CASE WHEN `timestamp` >=…
  • @MysteriousDomo try this: CASE WHEN `dt` >= SUBTIME(CURRENT_DATE(),7*60*60) AND `dt` <= ADDTIME(CURRENT_DATE(),7*60*60) THEN 'Include' ELSE 'Exclude' END SUBTIME and ADDTIME work in seconds so I am multiplying 60 twice and then by 7 to do 7 hours (I find that more readable than entering in the final number) This avoids the…
  • Here are a couple of ideas for you: There currently isn't a retry if fails option in Workbench, so you should submit this in the Ideas Exchange section of the Dojo and maybe it will be added in a future release. Consider increasing the frequency of your job schedule. Domo is smart enough to not process if no data has…
  • You can do this with a Group By tile and have your name and drink in the select list and then use Sum or Count as the aggregate on the field you want to total.
  • 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…