MarkSnodgrass Coach

@Domolex welcome to the forum (and there are no bad questions here). It is certainly smart to first try and build what you need off the source dataset and see if you can skip the ETL execution. To count distinct event ids you can create a beast mode that looks like this: COUNT(DISTINCT eventid) You can put your date on the…

I would check two things. First, make sure that the name of the field that is used in the dropdown filter is the same name of the field in the dataset that is powering the card. It is case sensitive. If the same dataset is powering the dropdown filter and the card, this shouldn't be an issue, but thought I would mention…

In order to add 3 days to the current date you would want to write it like this: DATE_ADD(CURRENT_DATE(), interval 3 day)

In your values section, if you click on the pencil for the percent beast mode you put in there and then click on Total, you can click the checkbox that says hide total. This will hide the total values from appearing for that field. However, the column heading will still appear. I feel like the fact that the heading still…

In your ETL, click on the Append Tile and then choose Include All Columns. This will allow all columns from all appended datasets to to be included. You can also review the other options available in the dropdown list to see if one is a better option for you.

I took your sample times and was able to add them up using the following in Magic ETL: Your group by would likely look different than mine, likely some sort of event id or something. I used split_part to break out the individual time elements and get a total number of seconds and then use the group by to sum it up. The…

I would use the UNIX_TIMESTAMP function for both of your datetimes, which will convert them into numbers. You can then easily subtract the two to get the number of seconds between the two and then use the SEC_TO_TIME function to convert it back to a time format. UNIX_TIMESTAMPIf called with no argument, returns a Unix…

Typically this message will show up in table cards where you are trying to display every row in a dataset. Domo can sum up millions of rows in a bar graph without that message displaying. Do you have something in your series or sorting that is not allowing the graph to aggregate? If there are still a high number of rows…

You can use the Domo Workbench app to do this. It is a small installable application that can do scheduling for you. You could potentially use the OneDrive Connector if you use OneDrive and your are storing locally in a OneDrive location.

Do you have anything in the sorting section in Analyzer? That will keep like items from being grouped together.

I only have experience working with SVGs for custom charts but geoJSON is supported. You can read about it here: https://domo-support.domo.com/s/article/360042924454?language=en_US Here's a video on creating a custom chart.

You will want to use this method that I outline in this video to break them up dynamically since you don't know how many there will be. @MayaU_01

My bad. SQUASH_WHITESPACE is only available in the formula tile in Magic ETL. Try this instead: UPPER(TRIM(`company name`)) Make sure what is inside the ticks is your actual field name from your dataset.

I would try troubleshooting by creating a beast mode that might help identify the issue. I would start by creating a beast mode that looks like this: UPPER(SQUASH_WHITESPACE(companyname)) This will eliminate any extra spaces and convert the string to upper case as Domo is case-sensitive when evaluating differences between…

Unfortunately, it looks as though the Sankey chart is quite limited in what you can use for hover text and tooltips are unavailable for the Sankey chart type.

I randomly run into this issue as well. Glad you are bringing attention to it.

@ArborRose when I inspect the network traffic when I click on a tag in the data center, I see that this is being applied. This would be against the https://[instance-name].domo.com/api/search/v1/query Have you tried using this already?

You are not alone in asking that question. The advantages of App Studio are improved branding and formatting control. It also has a better form module. It still lacks some features that dashboards have, but they are working on adding them. Many people wonder why they didn't just enhance dashboards with these features.

A couple things to point out for you on this: While you would need to use the Save As option to have a card display multiple times on a dashboard, when you create a beast mode, if you choose Save to Dataset, any edits you make to that beast mode will apply to all the cards on the dashboard. This may lower your maintenance…

I don't think that is possible with this chart type, but you could try using a beast mode like I suggested but rather than a constant value, create a long case statement where you are setting the value.

If I'm understanding you correctly, you want all bubbles the same size even though they have different values. You can do this by creating a beast mode that has a value of 1 and then put that in the values field and choose Min for the aggregation. You can then drag the value you want displayed into the tooltip 1 field and…

I would look into the custom charts option that is available. Here is a video about it as well as some KB articles: https://domo-support.domo.com/s/article/360043428793?language=en_US https://domo-support.domo.com/s/article/360042924454?language=en_US

Here's a video on how to split values dynamically when you don't know how many times you will have to split.

@trafalger just did this. He may be able to explain how he did it. I believe it required some programming within Code Engine to accomplish it.

If you click the wrench and choose Edit Drill Path there is an option to prevent drilling to the raw dataset.

Since this is a beta feature, I would recommend providing feedback to the beta team to let them know about this issue. Betafeedback@domo.com.

@GrantSmith is the king of API calls and may know if this is possible.

Agree with @MichelleH . Here is a video that walks you through it.

You can have multiple workbench installations, but having them run the same job would be problematic. I would recommend reviewing this KB article about migrating Workbench to help better understand what to watch out for. https://domo-support.domo.com/s/article/000005219?language=en_US

Try this: CONCAT(LEFT(TicketOwnderFirstName,1),TicketOwnerLastName)