MarkSnodgrass Coach

Each workflow has a settings tab which is where you can schedule how it should be kicked off. Your 2nd workflow can be kicked off by when your input dataset is updated. Choosing the Trigger of When Datasets Update and then selecting the appropriate datasets will cause your 2nd dataflow to once any of the selected datasets…

Displaying the quick filters directly on the card in the dashboard view is not currently an option. You could submit it as an idea in the Ideas Exchange as a future enhancement.

You can create a second card that uses the slicers chart type and have that at the top of your dashboard. This will interact with your main graph on your dashboard.

You can take your result object of your first workflow (which would be your output dataset) and make it the input dataset of your second workflow. To use these objects as "parameters" against your main dataset in your second workflow, you can set a constant of 1 on both datasets and join on that value. This will make it so…

Yes, you can do this with some of the dataset that are available in the Domo Governance connector. Specifically, you would want the Dataflow Details dataset and the Datasets Dataset. You can then build an ETL to let you know which ones are used and which ones aren't.

I agree with you that it doesn't appear to operating the same as the indicated definition in the formula editor. I would suggest sending it in as a bug to support@domo.com and see if they will fix it. In the meantime, I would use WEEK() as you definitely have more control with the extra parameter options.

Beast mode functions tend to follow the MYSQL definition. https://www.w3schools.com/sql/func_mysql_weekofyear.asp Where are you see inconsistencies? I got the same result in my card and the w3schools editor when entering in 6/19/2023.

Is it also possible that some of your rows don't have leading zeros and some do? If so, you can use the LPAD() function to add leading zeros if everything should be a certain number of characters.

Here are a couple common issues with joins in Magic ETL It is case sensitive Leading or trailing spaces An easy way to address both of these is to add a formula tile to each table prior to the join and use the following functions UPPER() - converts the text field to uppercase TRIM() - removes any leading or trailing spaces…

Here's another video walkthrough that may be helpful.

@deona720 I wonder if your canvas is too wide. Have your tried putting your objects into two rows on your canvas and see if that works?

@Edgar_Movius interesting. I tested on a table card on a dashboard and I was able to do it. I will try and record and post when I get a chance. Maybe check your interaction filter and see if that is preventing it. This is what my interaction setting looks like.

If you hold down your mouse click and drag, it will highlight the cells you want to copy. You can then press ctrl+c to copy the text and then paste it into Excel or wherever else you need it.

On the history tab of the dataset, you should be able to go over the right and wrench will appear and you can choose "delete this update"

You might also consider using the Form and Dataset Brick where you can have the users fill out a form and submit the data. You should be able to make a dropdown list of datasets so that the users don't have to locate the datasetid. You can then build cards off of the submitted data to manage the requests.

You might want to look into using the flex table to do this. https://domo-support.domo.com/s/article/360043429073?language=en_US

I tested with my faceted chart and it does seem like a bug that it is not letting you hide the value scale using the show label option. As far as working with what you have, what macro/value do you have in the data label settings? Whatever you are displaying in the black box inside the bar with the data label settings…

You can't truly omit those rows and still show the total, but you can click the minus sign next to 2021 which will collapse those rows keep the detail from showing. If you do this in analyzer, it will save as the default setting for the viewer of the card.

You may want to look into pfilters (or deep link filtering) to help you with this: KB Article: https://domo-support.domo.com/s/article/360042933114?language=en_US Video walkthrough:

I would then check what filters you have in place that might be keeping the data from being displayed. Check your date range filter and see if it has some hard-coded between dates or other date range limitations. Check your filters and try temporarily removing all of them and see if your new data shows.

If you scroll down below the chart, it should show the dataset powering the card and how long ago the data was updated. Does that match what you would expect?

I have found lately that when I change chart types, the fields to use don't automatically change to match the chart type until I drag a field into one of the areas. Once I do that, the appropriate fields show up. Seems like this is what @muahmmad_zaidi dealing with as well. It's a nuisance bug that will hopefully be…

Scott, One thing you can do is to use this FIPS CBSA crosswalk on this page. Ideally, you could find a svg files that has the excact CBSA borders, but one didn't turn up for me in a quick google search. Hope this helps.

The developer instance is free. There is no direct tie to your prod instance. You would need to manually create dataflows or datasets in each instance. If you are looking for migration options, you would want to consider the Sandbox feature, but it is a premium feature. You can read the KB article here:…

You can go to developer.domo.com and create a developer instance for free and then invite your users to that instance as your sandbox instance. You can then use your main instance as your prod instance and set permissions as needed.

I have recently seen Domo e-mails being help up in our Exchange Server's Quarantine which require your IT admin do release them before they would even have the chance to show up in a user's Outlook. If your organization is using Office 365, this would be in the Office 365 Admin Center.

On the Single Value Card, in the Chart Properties → General, change Divide Value By to None. This will make it so that it doesn't abbreviate.

If you are referring to formatting the number in the summary number, you need to click on Formatting Options and then uncheck abbreviate and place a check next to use thousands separator. If you are referring to a number on a specific card, please tell us what card you are using and we can tell you which chart property to…

As @GrantSmith said, this feature doesn't currently exist. However, you can do what you want to do by breaking up your ETL into smaller ETLs for testing. Then, once you have it all sorted it out, you can copy and paste the tiles back into your main one so that you have a single ETL for production. I would create a ETL…

In the data center, you can click on the key icon on the left to view the integration accounts. Look for your SharePoint account. If you are the owner of it, you can click on Edit Account and see the Client ID and Secret. You would then need to go to your Azure Portal and verify that the client ID and secret still are…