ST_Superman Domo Employee

Have you looked at the "View Page as Slideshow" option, or the "Publish as Slideshow" option?

Try adding a beastmode to identify the status of each issue: CASE WHEN `Resolved_date` IS NULL THEN 'Open' ELSE 'Resolved' END Then use this new field as the series

Mind sharing the beastmode? Might help understand what is going on

I'm guessing that you have two date fields in your data set. You will want to "stack" the ticket data so that you have a data set that looks like this: Spoiler (Highlight to read)SourceTicket…

Try something like this for dates from last saturday: SUM(CASE WHEN `date`=date_sub(CURDATE(), interval DAYOFWEEK(CURDATE()) day) then `greater than 70 days` else 0 end) If you need the saturday before that: SUM(CASE WHEN `date`=date_sub(CURDATE(), interval (DAYOFWEEK(CURDATE())+7) day) then `greater than 70 days` else 0…

You will need to do this through an ETL or MySQL data flow. If the ETL is taking that long, then there is probably something wrong with your settings. If you have any Domo consulting hours, you may want to engage that team to take a look at your ETL and see if they can find the issue. If you are comfortable posting the…

via Google Translate: When changing the column name in ETL "Select Column", I want the original column name to be entered as the initial value When changing a column name in ETL "Select Column", it is in the place of "Modified Name:" I want you to put the original column name. Or, I want a button to enter the original…

What your calculation is doing is looking at the minutes, finding the difference and taking the abs value. In your example, 59 - 2 = 57

Can you try using TIMEDIFF() instead? TIMEDIFF('Time 1','Time 2')

This isn't something that you can do within a beastmode calculation. Especially if you are going to perform further calculations on it. I would recommend creating a new data set where you agregate this data at different levels. (once aggregated by visit id, once by download id, etc.) You could use SUM(DISTINCT `Cost`) but…

I found this on another user board: https://forum.uipath.com/t/error-im004-microsoft-odbc-driver-manager-drivers-sqlallochandle-on-sql-handle-env-failed/79288/3 Had the same error when hosting .asp website that was making a connection to an Oracle database using the ODBC driver on Windows 2016 server. Found the below steps…

You can set min and max values for the axis, but I am not sure how to break the axis in the middle. Can you share what your use case is? I would probably recommend trying to break the graph by a series so that you could use two different axis. One for the lower values and one for the higher ones. I'm assuming that if you…

Actually, the more I thought about it, if the flex table is sufficient, you can create it without the ETL at all:

A case statement won't do the trick here. The basic reason is that when evaluating a case statement, you can only look at one row at a time. This means that you need your values for the previous month to be in the same row as your other values. You can do this via an ETL data flow with a few transforms: You can then create…

I agree with @guitarhero23 Until we get access to those pivot tables that were unveiled at DP, I don't think you can do this without putting the data set through a Dataflow (ETL or MySQL). Let us know if you would like help with the configuration.

If the dates are entered via UTC, then you don't want to use any timezone shift. The data needs to come into Domo in UTC. The timezone shift is in the event that the source system does not use UTC. The company settings will then let you specify that you want to view Mountain Time

Could you share a screenshot and a sample of your data set? Also, it would be helpful if you showed an idea of what you are wanting as an output.

Double check the values you are seeing too. I'm guessing that it is just pushing to forward 10 hours. That would change 2019-04-17 18:16:00 to be 18 Apri 2019 08:16:00 AM... not 18:16 AM. Either way, if this is a workbench job then I think the fix is to add a "Shift Data Timezone Transform" to your workbench settings: You…

It might have to do with the formatting for the field not being set once you remove the chart from the card. Can you try creating a beastmode to test as the summary number? Something like : ROUND(`Percent_Field`*100, 2) Then assign that value as the summary number and see what happens when you remove the chart. Let me know…

@DHB_1 - I didn't realize that these were coming from two different data sets. I noticed that in your example, you have the same date listed multiple times in the project tab. I'm assuming there is other meta data around those projects that are important to remain in the output of this join. If not, then you can skip steps…

Would you mind sharing a sample of your data set and the card you are building? I will see if I can walk you through how to add the filter beastmode I posted.

@swagner... Nicely done. I'll be using this tool a lot. Makes it much easier to create the deep links

You need to move the field name up in your query. It should end with ... Altify_Pause_Date__c, Lead_Source_Detail__c FROM Opportunity

The real issue here is that you have two date fields. You have to select one to build the card around, which is why I chose to cross join the calendar table so that all dates would be captured. You can then calculate the “active” number by comparing the open and close dates. 

 

Ah. That makes more sense. Have you tried using the "Scale Marker" chart property to display the goal?

I'm working on learning ETL. My mind just thinks more in SQL right now so it is easier for me to find solutions that way. ? If you want to show the ETL solution, that would help me learn as well! The more the merrier.

I decided to cross join your data with a calendar table to help me fill in each day an account was active. You can find the Calendar data set by searching for Domo in the cloud app connectors. Domo Dimensions has a calendar data set you can use. I then joined it in a MySQL dataflow with the following transforms: SELECT a.*…

What would you expect to see if the date range was: 1/4/2019 - 3/6/2019 Since Account 1 was opened prior to the date range, would you expect it to count because it was not closed before then end of the date range? Since Account 2 was active for nearly the entire period, would you expect it to count for this date range?

You should be able to accomplish this with a calculated field as a filter. CASE WHEN `date_field` < DATE_ADD(CURDATE(), INTERVAL 12 MONTH) AND `date_field` >= CURDATE() THEN 'Next 12 Months' ELSE 'Other' END This will calculate down to the day. You will need to change the logic if you are just interested in the monthly…