AS Coach

For now that's the only way. Annoying, right? PDP only instructs the browser what data a user can view, not that they have permission to view any cards built on the data or can access the dataset in general. There's likely an Ideas Exchange post out there requesting dataset access without card sharing. If you find it, make…

We also use Redshift exclusively. Our datasets range from dozens of rows to dozens of millions of rows. Some benefits for my perspective: 1) No indexing, less maintenance 2) Faster processing on larger datasets 3) Common table expressions, window functions, etc (mysql didn't have this previously, though I've heard that may…

To my eyes that passes all tests I would undertake. It definitely might have to do with the free plan. Maybe @DaniBoy can rustle up some resources to give you a definitive answer.

You're right to join on date and any other common column you might have, like segment or whatever. Make sure you don't miss any join conditions or you'll get more data than you want. You probably need to also make sure that you've aggregated the transaction detail up to that daily summary level, like the GA data is.…

This date selector should show up for most cards unless the option to turn it off has been selected. That option is at the bottom of the Date Range menu on the card analyzer view and is labeled as "Hide Date on Card Details"

Hi @debbie_a It's found at the bottom of the card analyzer page in the Data Table section. Top left of that is a box that says All Rows. Click on that and adjust the number of rows that appear in the output.

These are issues for sure. DataFusions are fast and helpful but have limited functionality compared to SQL and ETL dataflows. You could try those methods instead. Make sure to also submit this request on the Ideas Exchange for others to indicate interest as well.

Can you tell us if the sales column exists in the second dataset and if it has the same name as the first data set? That's the first place I'd look.

If you want to do an aggregation on data where certain conditions apply, you usually have to do the aggregation on the outside of the case statement instead of on the inside. Yours should look more like this: AVG(CASE WHEN `acquisition_cost` > 1 THEN `acquisition_cost` END) * COUNT(`property_id')

The Domo email connector is only able to download attached files, not attached files behind credentialed links. You'll have to take a different approach.

That's a good question. I can't give you a reason except to say that map charts are more like heat maps in that color saturation relates to the aggregated amount ranges. You can't override which hues apply to which ranges. It probably has to do with Domo's insistence on simplicity.

Eventually we'll probably see SQL transforms in Magic ETL (so the rumor goes), which means we could have the best of both worlds. I have my fingers crossed, my hopes high, and my expectations in check.

No problem. Domo's a company that listens pretty well to customers, especially influential ones at that. They take feedback well. Like most growing companies, the backlog is long and prioritized. So if you can get visibility to your problem, it will receive the development effort you want. And as always, it helps to know…

Hi Srujana You'll want to use a SQL dataflow for this instead. ETL only allows limited join options, like you stated.

Unfortunately this is not a capability Domo has at present. That said, there are several similar topics proposed in the Ideas Exchange here in the Dojo. Go check those out and upvote them for more attention.

You're very welcome. There are a few ways to get that feedback to Domo. One would be the Ideas Exchange here in the Dojo. There, others can upvote your idea, and that garners attention from Domo product managers. The more votes the better, and your Dojo status increases with more likes. Another avenue would be simply…

In my time as a Domo employee and since then, I have never heard a request for additional PostgreSQL capability. Not to say it hasn't happened, but I don't think it's common. You should probably provide feedback to Domo, though, to make sure your voice is heard. Dataflows don't much care what kind of data you put into…

Hm. Make sure you don't have any filters or sorting in place, and you're looking at all time, not just one particular day. Aside from that, if you're using an aggregation in either the beast mode or the column configuration, the table should add up all of the differences for every dimensions you've added as extra columns.…

What would you want your pie chart to look like? A breakdown of counts of individual scores across every site and rating number? In your case below, that would mean of 54 responses, 19 were Mastered, 13 were In Place, etc. If that's the case, you might have to rearrange your dataset first. With the pie chart, the card is…

What kind of chart are you using and which of the suggestions did you use? Any filters in place?

Hi Rafal Your second option is the preferred option. Domo will read the rows of data independent of how they nest under preceding rows. In other words, Domo won't know that B11 is part of A1.

As simple as this maybe: `available column` - `used column` That would give you the difference on a row level If you ever want to display these amounts across several states or across other dimensions, then maybe aggregate it up like this first sum(`available column` ) - sum(`used column`)

That's something you'd probably need Domo Support or your success manager to help you with. The configuration options aren't open to the actual customers. Weird.

Is your `Item No` a text field? If so, you probably can't sum that. Try COUNT(`Item No`) / COUNT(DISTINCT `Customer ID`) That would be to show the number of products purchased by customer. Depending on the use case, you might also look at SUM([quantity column]) / COUNT(DISTINCT `Customer ID`) That would get you the…

Duplication might be reduced naturally, depending on the direction and cardinality of the join in your ETL join transform. If you're willing to share a snippet of sample data we could probably look at that more closely.

In some cases like this you have to join your sales data with a calendar dataset that has all days in it. That way you'll have records of days with no sales data, but at least something is there when you have no sales. Luckily the horizontal line and bar charts are pretty good at representing the same thing without that…

The only way in Domo to have datasets affect each other is to join them using a dataflow. You can set up a dataflow with a join a lot like that, and create a third output dataset, C, with which you'll build your cards. That way whatever states are in source B will affect how A and B produce output C.

It sounds like you'd require beast mode to link aggregated data to a particular row of data to make the comparison and that would take some nesting logic. This kind of looping is best done in a SQL dataflow or in a custom app. Beast modes can't nest like this at present.

@michellelem, that property has received a new label. "Series on left scale" is what you're looking for.

This is one way to do that: str_to_date(concat(year(curdate()),'-01-01'),'%Y-%m-%d')