MarkSnodgrass Coach

In the sorting properties, drag your date column in and sort by ascending, then drag in the column you are using for the series into the sorting properties below the date column and choose ascending. That should do the trick. If not, please provide screenshots to make it easier to see what might be going on.

You could do this in a beast mode and it would put it in the 24 hour format without the date: DATE_FORMAT(fieldname,'%T') or this to put it in the AM/PM format: DATE_FORMAT(fieldname,'%r')

@faisalnjit if you haven't installed the Domo Governance/Domo Stats cards and datasets in your instance, I would encourage you to do that. This will help you see which pages and cards are being viewed the most and which users are accessing them the most. As far as dev vs prod, I don't think there is one set best practice,…

They announced at Domopalooza that dashboards can be set to auto width instead of fixed width. I see the capability in my instance, so I assume it is deployed to everyone. Click on Edit Dashboard, then under Options, choose Display Mode and select Auto Width.

There is not a direct integration for pull requests, but you may be able to leverage the Domo CLI tool to pull of what you want to do. It is located in the Admin - Tool Downloads section of your Domo instance. You can read the KB article about the tool here.

Have you tried the Bullet Chart? That might be a good fit for what you are trying to do.

You can select all the items in your Magic ETL and then choose copy to clipboard and then paste it into any text editor and it will copy all the logic to the text file that you can save for later. You can then paste it back into another ETL if you wish to use it again later. The output dataset will remain intact if you…

Unfortunately, CSV is the only file type the Scheduled Reports will be attached as. See the KB article: You can still open a CSV file in Excel, though.

Doing the aggregate I suggest will drop the movein, moveout, and transfer columns and just leave you with the SiteID, Batch Last Run and your aggregate count.

In the ETL, add a Group By tile and put SiteID and Batch Last Run in your select columns and then choose Count and SiteID for the columns to aggregate. In your example, this would give you a count of 4 for Site 3196 for that day. If you want it to have a count of 1 for Site 3196 for that day, choose Count Distinct values.

Unfortunately, the beast modes will expand out when you include them in another beast mode. I agree that it would be really helpful if they did not do this, as it would make the code a lot cleaner and more efficient. I'm not sure if it has been submitted in the Ideas Exchange section of the Dojo, but I will definitely vote…

You can do this in Magic ETL or in a Beast Mode if you get a feature enabled. In Magic ETL, you can utilize the Group By tile to sum up totals by month and year. You can then use the Rank & Window tile and the LAG function to put the previous month total next to the next month and then calculate the difference. In Beast…

The information you provided is pretty vague, but if your source data comes from Domo Workbench, I would open up Workbench and check to see if the schema changed on that job and then refresh the schema in there by clicking the preview icon and then running the Workbench job again. If that is not it, I would just try…

Good question. If your source data is level-setting to UTC, than it seems like you would be okay, but I would do some test on that. You could build the logic into your formula tile if you do need to adjust for it because you can use the MONTH function and the DAY function to determine if you are in the daylight savings…

The convert_TZ doesn't want the friendly timezone names. It wants the hours you want to move from to and should look like this: CONVERT_TZ('2008-05-15 12:00:00','+00:00','+10:00') You could create a simple lookup table that would have your timezone id name and have the number of hours from UTC that it is as another column…

I have the Magic ETL 2.0 beta and it is still a manual process as well. It is interesting idea and you might want to submit it in the Ideas Exchange section of Domo for future consideration.

You might be able to do this if programmatically via the Domo CLI or API tools. Within the main Domo Magic ETL interface, you must manually name your output datasets.

Add another column that aggregates a field by using the count or sum, for example, and it will remove the duplicates. You can do this by dragging another field over and then click the pencil icon next to it and choose one of the aggregation options. Make sure you don't have anything that is in the sorting properties

@Anna Yardley I completed the survey. Thanks.

that indicates that the column name item is in more than one table. You can remedy this explicitly stating the table name and column name in this format: tablename.columnnname wherever you are referencing a column. You can also alias a table after declaring it to shorten it when you reference it elsewhere. For example, you…

Domo uses MySQL 5.6, so any time you wonder what syntax you should use, just google the reference docs for MySQL 5.6. Looks like you need to use the LIMIT clause in MySQL, so your query would need to be changed to this SELECT `Item Trim_Fill Rate`, `Trim Whse`, `Ship Date` FROM `copy_of_cuts_w_forecast` JOIN…

Have you tried using the MIN function on the date field you want the earliest date from?

@user048760 If you have the Magic ETL 2.0 beta, you can set as Date when you click on the input dataset configuration. If you have the regular Magic ETL, you would add the Set Column Type tile and select your column and tell it to use the type of Date.

Unfortunately not. I think it is Domo's way to give you a quick glimpse of what the card will look like, even though it rarely correctly selects the fields that you intend to use. You can turn off the auto preview option when in the Analyzer, which will make it quicker for you to change what fields you want to include in…

@user048760 I use that same connector with the append and I use the batch_last_run to identify the groups and when they were added. There are a variety of date format options you can use in the Analyzer and in Magic ET if you want to get rid of the time portion of the batch last run column. In Analyzer, when you add the…

Great work @sem ! Glad I was able to help.

I'm not sure you will be able to do this in Analyzer/Beast Mode, but I will help you as much as I can with the following information. First, you will need to ask your CSM to enable Window Functions in Beast Modes if you haven't already done that. To get your percent of total, you would need to create a beast mode like…

You should look at the Domo Governance / Domo Stats datasets that are available in the app store. Search the app store for Governance or Stats and you will see the different datasets that are available to you. They provide a lot of this information for you as well as some pre-built cards. You can then tweak the cards if…

You should look at the Domo Governance / Domo Stats datasets that are available in the app store. Search the app store for Governance or Stats and you will see the different datasets that are available to you. They provide a lot of this information for you as well as some pre-built cards. You can then tweak the cards if…

Yes. That is the correct way to do it in SQL. I prefer Magic ETL because it tends to run faster.