MarkSnodgrass Coach

This idea has already been submitted here: Consider adding your vote to this idea and hopefully it will be implemented by Domo at some point.

When using Bricks, you will be querying your data using the JavaScript section of the brick. Your question really becomes a JavaScript question. If you haven't reviewed this section of the Domo Developer Docs, I would recommend looking through their tutorials.…

I don't think there is a way to be notified that a card doesn't load. To fix the issue, edit the card and the issue should be highlighted when you are in Analyzer. I have also seen this happen when the dataset has not been accessed in a long time. To fix this, you need to go to the dataset and click "start" (I believe) to…

Is there a specific error message that is displayed when you try to save?

Similarly, you can do: DATE(CONCAT(`Month`,'/1/',`Year`))

@jaeW_at_Onyx has compiled a pretty solid library of API endpoints. Here's a link to it:

You can use the HOUR function in a beast mode to extract the hour of the day out of your datetime field. You would then put this beast mode in your x-axis. Beast mode would look like this: HOUR(startdate)

You need to go to the accounts section in Workbench which is the key on the left side and then re-authorize. It will typically open up a browser window and have you put in your Domo credentials to authenticate. The easily missed step is clicking on the Save icon in the top right of Workbench after you finish the browser…

It seems like you have a running total option selected. Assuming you are using the Line Bar chart type, go to your Chart Properties and make sure the Number of Running Total Bars is set to None.

Great post! Thanks for documenting this for everyone!

I walk through how to do this in this video:

Yes, you can do this using the Variables feature. Here's an overview of how to use them.

I think you are going to want to look into the fixed functions feature for this. https://domo-support.domo.com/s/article/4408174643607?language=en_US You may also want to look into the segments feature. https://domo-support.domo.com/s/article/4403089503383?language=en_US

I agree that it could be improved. You can use traditional SQL or their Data API syntax. These links on the developer.domo.com site should help you. https://developer.domo.com/portal/8s3y9eldnjq8d-data-api https://developer.domo.com/portal/6fa7587d4c2ea-querying-data…

You might try changing the inner joins to left joins and then use a filter or remove duplicates tile to get to your desired result.

I would re-write them to use IN and NOT IN like this: CASE WHEN GL Group Code NOT IN (170, 175, 190) and Current Balance >=100000 THEN '01' ELSE 'N' END CASE WHEN GL Group Code IN (170, 175, 190) and Current Balance <100000 and Current Balance > 0 THEN '02' ELSE 'N' END

You can use two join tiles and do an inner join on each. the first one joins ID → New ID and the 2nd join tile joins ID → Legacy ID. You would then use the append tile to bring the data together. Would look something like this:

I was just looking into some remote triggering of Workbench jobs and one of my Domo contacts thought about Workflows as well. He did some asking around with the Domo engineers and was told Workflows would not be able to help in this scenario. There is a beta of Domo Workbench Enterprise that might be worth looking into. It…

I have been able to use the HTML br tag in summary numbers to do line breaks. Like this: CONCAT(IFNULL(Street1,''),'<br />',IFNULL(city,''),', ',IFNULL(state,''),' ',IFNULL(Zip,''))

Like this: CONCAT(IFNULL(Street1,''),' ',IFNULL(city,''),', ',IFNULL(state,''),' ',IFNULL(Zip,''))

CONCAT can have trouble dealing with nulls, so I would suggest wrapping each element in IFNULL and replace it with an empty string, like this: IFNULL('zip','') Hope this helps you.

All ETLs have settings that allow you different ways to control when you want your ETL to run. When editing the ETL, you can click on the icon that is just to the right of the zoom controls (it looks like 3 lines with dots on them). I would suggest having it run whenever either dataset is updated. This will ensure you…

You would need to combine the data in Magic ETL so that it is one dataset. You would have two input datasets: order detail and sales goals. I would use a formula tile on your order detail to get the first day of the week for each order. You can use the following formula to do this (replace dt with your actual order date…

You could look into utilizing some of the Domostats tables to at least alert you which cards are tied to a dataset that just lost its certification. Would take some work. I agree that it would be a nice feature to be able to toggle if you want things downstream to be automatically de-certified.

In the Workbench job, under Configure and Additional Settings, you can change the When To Terminate Long Running Jobs to 1 hour. This should trigger a failure notification for you. Also, under Transforms, you can add a Calculated Field and add a timestamp column with the NOW() function. You can then create a card that…

Try this, though you'll need to re-type the index and variable fieldnames if they don't paste in correctly. SUM(CASE WHEN index >= date AND index <= DATE(CONCAT('12/31/',YEAR(CURRENT_DATE()))) THEN variable END)

an easy way to get the last day of the year is to do this: DATE(CONCAT('12/31/',YEAR(CURRENT_DATE()))) You can put this in place of your 2nd date piece.

Unfortunately, the smart text doesn't support this yet. If there isn't already a submission in the ideas exchange, I would suggest adding one for this.

I would review this KB article on Workbench partitions and see if that works for you. https://domo-support.domo.com/s/article/360062446514?language=en_US

If you are using Domo Workbench to push your data to Domo, you can use Partitions to just send the new data. Magic ETL also has partitions. You could also use the append option your dataset so that it would continue to add to your Domo dataset.