ColemenWilson Coach

The solution is to export the card, not the dashboard. When you export content as a PDF, Powerpoint, Scheduled Report, etc… it creates a static export that you cannot interact with as you can in Domo. For this reason, table cards that have over a certain number of rows will be cut off with no scrolling functionality. If…

Here's what I came up with on how to solve this: https://youtu.be/EnN4zuXVkRI

I knew I'd be dethroned at some point but didn't think it would happen so quick! Nice work @david_cunningham !! Congratulations on the coach status!

I've recorded this video walking through how to do this: https://www.loom.com/share/06479b81c71143f28a503c5081b49e7e?sid=5eba93fa-e6e3-43bb-abc0-4a239d97a2ff Let me know if you have any other questions!

If those are the only letters that will appear in the values of that field you could create a beastmode: CASE WHEN `ItemNumber` LIKE '%A%' OR `ItemNumber` LIKE '%B%' OR `ItemNumber` LIKE '%C%' OR `ItemNumber` LIKE '%P%' THEN 'Out' ELSE 'In' END

This is already possible using Brand Kit. If you don't have brand kit currently, you can reach out to your CSM and they can get it enabled for you.

I believe so, and if it isn't you could sign up for a Domo Freemium account where it would be: https://www.domo.com/start/freemium But here is where to look in your current instance:

Yeah, that is what all users see - the standard default drill path. Your options are to create a custom drill path (as you pointed out), disable drill paths, or keep the default. You could also submit improvements to the default drill view as an idea in the ideas exchange.

Could you provide a screenshot of what you are seeing? Just want to see if it is the same view the rest of us see or something different.

@Chris_Wolman Awesome! I stand corrected!

It could if you have beastmodes saved to the old dataset that are not in the cards/dashboards. But if they are saved on the cards and the fields stay the same, they should still work. Definitely test with 1 ETL before switching them all over!

You'd have to create a new dataset via Workbench, once done you could swap the datasets in your ETLs. As long as the schema is the same, it shouldn't have a negative downstream impact.

You would use the pivot/unpivot tile in Magic ETL: https://domo-support.domo.com/s/article/360044951294?language=en_US There are examples in the KB article that walk through exactly what you are trying to do. Let me know if you get stuck!

You'll need to make sure this is enabled in your instance (in Admin) to be able to send scheduled reports to folks who are not a part of your Domo instance:

No this is not currently possible. You could organize them using a naming convention, something like: "DIMENSION: Sale Date" or "MEASURE: Total Sales" etc… You can also add Tags and descriptions to fields to organize them.

You can join with a calendar, and then aggregate to the date in the ETL to reduce the row count. You'd sacrifice filtering (on the card) for row count savings, but if row count is a concern then that would be my suggestion.

Okay for your summary number use this: AVG(COUNT(DISTINCT 所在库位) FIXED (BY Date)) That will give you the average unique count over the entire time period by date for the group total.

It appears that Atlassian doesn't allow for Confluence pages to be embedded externally, unfortunately.

We use MS Forms extensively. The easiest way to pull this data into Domo is to sync the survey results to an excel file in OneDrive and use the OneDrive for Business connector. There is no MS Forms connector. One isn't really necessary since the OneDrive for Business connector is a direct connection to the survey data…

@dlc3 Amazing solution! Going to be using this for sure!

Figured it out, but you'll have to use the Advanced SQL Editor in dataset views. Once a dataset view is converted to an Advanced SQL dataset view it cannot be reverted back. https://domo-support.domo.com/s/article/360046074774?language=en_US#advanced_sql_editor

You could make duplicate views and bring those in as additional datasets to join twice more.

Ah I read your question wrong. When I've done this in the past, it has been static. I've done things like this: CASE WHEN `date` >= CURRENT_DATE() - INTERVAL 28 DAY AND `date` <= CURRENT_DATE() THEN `value` ELSE 0 END I can't think of a great way to make it dynamic. Hopefully @GrantSmith @MarkSnodgrass or @MichelleH have…

Date - INTERVAL 28 DAY Then, use the new date field above in your visualization, but filter using the original date field.

You can't do WHEN Sort: Month Number = 1 THEN NULL You could do WHEN Sort: Month Number = 1 THEN ''

It is because those are not Google Sheets, those are Excel files stored in Google Drive. Convert them to a Google Sheet and you will be able to find them using discovery in the Google Sheets connector.

Because you want to see the two combinations simultaneously, you'll need to combine the two columns. I did this using CONCAT(). I don't think this is the perfect solution, but it works. If you have many combinations of Cat and Name then this may not be ideal. Create a beastmode: CONCAT('Cat = ',Cat,' & Name = ',Name) Make…

You can use the following beastmode to correct the date: date_add(date('1899-12-31'), interval floor(あなたの日付フィールド) day)

To refresh your google sheets dataset: 1. Go to the data center: 2. Locate your dataset and click into it. 3. Then click the kebab icon in the top right and click "Run Now" If you data is an ETL output, you'll need to repeat steps 1 & 2 above and then: 4. Click the kebab icon and click "View Dataflow" 5. Click the kebab…

You can rename the fields in MagicETL. You just have 1 date from each datasource right? So for example, if in Dataset 1 the date name is Date1 and in Dataset 2 the date name is Date2 you could rename the date field in each to be New Date. Then union the data together and Domo will match up the date columns as a single…