ST_Superman Domo Employee

When you call the procedure, don't use the ; CALL transpose() This should be done as a SQL transform step.

Can you share the chart properties? Are you sorting by anything?

Try creating a beastmode that will mark the start of each week. You can then sort by this first, and then sort by your second beastmode. start_of_week : SUBDATE(`Date`, DAYOFWEEK(`Date`)+2) Then, you could sort by start_of_week and then by your calculated field. That should get you what you are looking for

I think the issue here is that you can't name a beastmode from within another beastmode. For example, if A in this case was something like: Current Year Sales: sum(case when `year`=year(curdate()) then `sales` else 0 end) and B were something like: Current Year Expenses: sum(case when `year`=year(curdate()) then `expenses`…

Have you investigated the CLI tool? If you have the list of cards you want deleted, the CLI should do the trick. I think you would need to reach out to your Customer Success Manager to get the install file. Ask them for the Command Line Interface tool.

Unfortunately, I am not aware of any way to allow user defined variables in the Domo product. You may need to create a custom app to accomplish what you're looking for

@Otieno_Onyango please let the dataflow run to completion to see if you still get different results. The preview engine in Domo does not always load the entire datasets. It just loads a small portion of them to minimize processing time. See if you still have the issue after running the complete dataflow.

@nicolac You should be able to get the results that you are looking for with @GrantSmith 's suggestion. I have done something similar to measure page, or card views within Domo. I use COUNT(DISTINCT `UserID`) to show many how many different users view the page, and then COUNT(`UserID`) to measure how many page views those…

There should be a "Manage Pages" link at the bottom of your Dashboard list: From there, you will be able to delete the page, or dashboard that you created.

If you are wanting to keep the NULL values, you may want to try adding two options to your filter card. NULL values do not play nicely when checking if they are equal to anything. In addition to the id NOT EQUAL value, try including id IS NULL Then set the filter rules to look for data that meet ANY rule.

@mberkeley there is also a beta product that would address this issue. I'm not sure of the timeline for a general release, but you could email chuck.irwin@domo.com and ask about the "Filter Exceptions Beta". I would at mention him here, but I can't remember his Dojo handle. You could also check with your Domo Custer…

@HowDoIDomo - I will often use the full outer join when creating a dataflow in ETL. I also will include an output dataset after each join. This helps me make sure that I am joining the data correctly and the number of rows are what I expect to find. The advantage to the full outer join is exactly what you mentioned in your…

@richardjmarshall One piece of advise that I would offer. And this is just to provide some more clarity and flexibility to the field that you are filtering on. I would recommend not just using 'THEN 1 ELSE 0' CASE WHEN LAST_DAY(CURDATE() - INTERVAL '2' MONTH) = LAST_DAY(`Date Field`) THEN '2 Months Ago' ELSE 'Other' END…

@GrantSmith - The plugin tool that I was referring to was the "Domo Admin" tool. This tool is not available to download from your Domo instance. You need to request the file from a CSM or technical support.

@user06209 There is a Domo Admin excel tool that allows you to do just that. I believe that you have to provide an access token (which you can create in the Domo Admin section) in order to get it connected. Otherwise, you could get the domo governance data offered in the data connector cloud app library and export that…

Would you mind providing a fake dataset that would mimic your data's schema and would provide enough fake data for us to work with? I wouldn't mind taking a stab at this. I agree with @GrantSmith , I think you'll have the best luck with a grouped and stacked bar chart. The issue with the regression line is that you can…

@serendipity This is an interesting use case. Unfortunately, I'm not aware of any ability to limit field access or to define a user specific drill path. I wanted to comment, though, because I want to make sure to follow along and hear any solution that is offered. This may end up being a feature request though.

@HowDoIDomo - Are you looking for a trendline for the total? Or are you expecting to see separate trend lines for each series in your grouped bar chart? Also, would you want the trend line to respond to filters? or card interactions? In other words, let's assume we are graphing sales performance by region. The trendline…

yes, you should add a calculated field that counts the number of rejected items you have. SUM(CASE WHEN `RejectedStatus`='Y' THEN 1 ELSE 0 END) Add a calculated field like this as a summary for the table and you can then create an alert that will let you know anytime that you have a rejected status. You can set the alert…

Agreed. Adding visibility to which datasets are powered by a workbench would be a big plus. Thanks @Ashleigh

This sounds like an issue with the actual connector. I would recommend reaching out to Domo support to see if they can troubleshoot the connector for you.

I would recommend using Magic ETL for this as that would allow you to use regex expressions to find cases where there are 9 or more digits. I'm not an expert with regex, but something like this may work: ^[-+\/\s]*([0-9][-+\/\s]*){9,}$

It looks like this has something to do with the way each query engine is processing the time values. Would you mind sharing the syntax for those fields to get a sense of what is being calculated?

I agree that the options to control how the data looks is very limited for a lot of card types. Flex tables are no exception. The only place that I could find to denote a scale abbreviation is in the summary number: However, this has no impact on the data in the table.

I prefer to draw out my metrics before getting started in Domo. How would I like to represent the data, what questions will different visuals answer. Once I get a good idea of how I want to present the data, I then start thinking about how to build that out in Domo. Is it a single card? Or would it work better as a story?…

You should also be able to do this using the file connector. Just click on edit selection and have the header include both rows:

What does it look like in Domo after you use the file upload?

@andres - it's not so much a bug in the HTML table cards as it is a specific feature that was added to mega tables. Prior to mega tables, the only option for a table card was the HTML table. In order to scroll you have to expand the card an looking at the card details.

I'm not aware of a way to do this. You can save the calculated field to the card or the dataset. If you have dataset views available, you could create a view of the dataset and add your calculated fields to that view only. Then you would only be sharing the calculation with any cards using that data set view.

NORM.S.INV() ... I believe is just the inverse of the CUME_DIST() function that you found in redshift. I'm not sure why your formula is adding 1.5 to the end either.