MarkSnodgrass Coach

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.

Do you have anything in the sorting section of the chart properties? When your x-axis is not a date, Domo usually needs something in the sorting section to ensure that the x-axis is sorted in the way that you would want it to.

You can't add it to the data table, but you could add it to the tooltip fields and then show tooltip field 1 with the data label sttings or hover text settings.

Great idea!

My first suggestion would be to do the calculation in Magic ETL, but that may not work for you depending on how you want the card to function as far as filtering You might try restructuring your case statement and see if that does the trick. If you can get your objective within your division calculation so that your are…

If you add your objective column to the table card, will that show that there is a month "repeating" because there is a different objective type?

@jmathers Yes, you can do this very easily. First, to restrict faculty to only seeing their students, you would need to set up the appropriate Personalized Data Permissions (PDP) policies. Once that is in place, you can use the table card to show only people with a passing grade, or you could use color rules to highlight…

Check to see if you have any fields in the Sorting section of the Analyzer. That will throw of how Domo can aggregate the data in the card. Also, check the Date Range Filter and what it is grouping by.

It does seem like a support ticket is in order. Mega tables are limited to 100 columns so you are pushing they edge. It is likely that they didn't test on edge cases with whatever recent enhancements they may have done.

If you have a list of all divisions than you can create a Magic ETL dataflow to do a left join to your form data and then filter where the form division name is null. This would give you a list of divisions that haven't completed it.

@loganherzog Does your card have some data in it that might be problematic? Is this a pivot table card? Or just a mega table card? I would try recreating the card and see if the issue still occurs. Sometimes a card's properties get corrupted and I just end up re-creating the card. If you still encounter the issue after…

@MichaelClark since it is top down, the .05 will stop at .06 and would not evaluate any lines below it. Happy to help!

Case statements work from the top down and exit out as soon as they find a match, so if you put your statement in a logical order such as evaluating from smallest to largest, you can properly work through the different scenarios. In your scenario, I'm guessing you want "Good" to be less than .06, "warning" to be less than…

In the chart properties, go to Data Label Settings. In the text box, click the + sign and choose Percent of Category.

MySQL has a DATE_SUB function that would work for this. Try this for your where clause: WHERE `date` > DATE_SUB(CURRENT_DATE, INTERVAL 7 DAY)

@Jessica Sorry, I thought you wanted to export the Workbench logs that are stored on the computer running workbench and upload them to Domo to analyze them. That is what I explaining how to do.

I have many summary numbers that are using currency and they are only show $xxx. I looked around in the company settings, but I don't see anything that would relate to specifying the type of currency being used. Have you tried a different browser just to make sure it isn't a browser plug-in that is doing this and not…

I think this looks like something Domo Support will need to look into for you. I would start with them.

I think you will need to remove them at the dataset level and then add them back individually to cards that should have them. If you go to the dataset in the data center, you can click on the three dots and click on Chart Color Rules. This should which rules are tied to the dataset. You will want only want to have rules in…

Agree with this suggestion. Up vote isn't working for me right now.

@dacorson Currently, Magic ETL does not provide this directly. You can get around this by adding a constant before your join and then filtering after your join. This is how I solved it when I need to use a BETWEEN operator on my join but you can't do that directly in Magic ETL. You can see an example of how it was done in…