Comments
-
The solution we have been told for years has been to 'just have different email addresses for each instance.' That is so unworkable for consultants that it's not even funny! How sweet would it be if any instance where your user id is the same email, it used the same password? Basically the opposite of how it is now.…
-
We've been suggesting a 'View Only' level of access for datasets for YEARS! You make an interesting point, though. People would still need to be able to share datasets in most cases, and that comes with the ability to unshare. Thinking through the back end of this may get complicated because if they can build something and…
-
You can also trigger them on your own schedule from a server or using windows scheduler and the CLI.
-
That is very strange. It looks like it's maybe including the difference in the number somehow. I tried a few different calculations to see if I could do some hinky math to ascertain what is happening, and no dice! I recommend opening a support ticket.
-
The old version used to ask if you wanted to update the data, but I am thinking from you question that this no longer happens. Sorry to hear that. What limitations prevent you from displaying the data in Domo? We may be able to solve for that, too.
-
I have heard that the functionality you are looking for is coming. At this time, when you select a beast mode to include in a subsequent beast mode, it just inputs the formula, as you have seen. I didn't see this in the most recent release notes, but I am told that this functionality is getting ready for testing.
-
It will be called 'PAGE' because that is what dashboards used to be called. For the metric you are looking for, I recommend using the 'Pages' dataset instead of the activity log.
-
We've been asking for this for YEARS!
-
That's how I do it, too. It's annoying to not be able to just click on it and change the dataset, but I can see why they did it that way. A new dataset would likely automatically update the alias and break everything. The solution @jaeW_at_Onyx suggested works perfectly every time, as long as the new dataset has the right…
-
One shouldn't have to go deep to achieve such a basic end. Also - I don't think the toolkit does that and it's a premium feature. It would be great if PDP rules could simply have a 'copy to dataset' option right there in the UI.
-
It doesn't have that? That's simply not logical.
-
When they are developing functionalities, I wonder if they really think about the most likely use case. Every other filter mechanism is for including, except that one, and it's strange. I always figured it was a bug.
-
NECESSARY!!!!!! Sometimes there are 100!
-
I hit ctrl+z all the time forgetting that it will do NOTHING!
-
This should not be tribal knowledge, and it totally is. Also, the explanations and examples could be much improved. But - first things first…tell us our options!
-
So much cleaner! And it could just be right there in the tile under the beast mode name and pop up when you hover, just like any dataset field. YES PLEASE!!!
-
It almost always picks the dumbest fields possible. Like - Let's say it's transaction data…It will give you something like: Bar chart with the vendor created date (or most irrelevant date possible), value as the sum of item number, and series of transaction id. It boggles the mind, and I wonder what the backend logic is.…
-
This is another idea that has been requested time and again. I think @Ashleigh has requested it a lot previously. (If it was someone else, oops!) I find myself wanting it SO OFTEN! Addendum to the screenshot above - I would like to see it not necessarily fully detach the sections, but to simply be able to identify sections…
-
They have been adding clicks to EVERYTHING in the last year.
-
They have brand kit, but from what I understand, it makes you lose all of the standard colors. It would be amazing to have an additional row of colors that are custom for the instance so that branding can be done without messing up every existing visualization. (Which is what happens currently.) Plus, this should not be an…
-
Yes! If you are global, these are things that have to be considered.
-
PLEASE!!! For the love of all you hold dear, Domo…Please give us this! It's been requested for many years and is standard in any coding that's done. Doesn't seem to make sense that this capability is lacking.
-
You mean putting your finger on the screen and scrolling to assess alignment isn't a good enough solution? LOL
-
FYI @trafalger - that link doesn't seem to work for me. Says it's unsafe.
-
I agree that the single line suppression does NOT do the job. It helps in rare cases, but generally just makes things more confusing.
-
How would you see that playing out? You mentioned time frames, but I am not sure how that would be set up or applied. Right now, for dataset level notes, I use the dataset description. I think that would be something that would be relatively easy for Domo to propagate out to cards via the card description. It could work…
-
This wouldn't be something in Domo's control. The best solution I have found is to simply have the email address of your dataset added to the distribution list for the email you are wanting automatically imported into Domo. Otherwise, it has to be done from your email platform. For any emails where the above solution is…
-
I agree with Mark's solution, and would add that in your grouping, you need to be cognizant of any other attributes you are capturing. For example, if there are multiple user names associated with an email address, what is different between them? Are their position, department, manager, etc., included in with the user name…
-
@Ben_Dunlap - I strongly concur with the rest of the folks here that you should give Magic another shot. 7 Million rows isn't a very large dataset, so even if you just use Magic when you need performance, it would help. If your analysts aren't interacting a lot with the end-users, SQL can make sense as a way to leverage…
-
Plus ability to select multiple accounts and do a bulk action.