DataMaven Coach

PLEASE!!! THIS!!!!

@JordanJensen - I think the word 'impersonation' has been taken too literally. We need to be able to see what a particular user or role can see. If someone wants to act on behalf of another user at some point, that is another discussion. A pretty high level of complexity is possible with PDP, and not being able to validate…

@BenSchein - Here's that idea you want to upvote!

@Engineer_0 - That wouldn't be a 'we' thing, though, since Overview and Favorites are personal to each user. It really depends on the access levels of the end users because if they have the ability to create pages, they should be doing so. Overview is basically a development space that ideally would not have much on it,…

PLEASE!!! This comes up so much!!!!

Agree! The alignment is a nightmare! For anyone Domo-side who wants to test it, find a dashboard with text boxes in it and look at it on differently sized screens. You will see that the carriage returns on text boxes are in different places. Depending on that spacing, you will end up with scroll bars where they would not…

What are the multiple steps to add a card to Favorites? I just tested, and you click the wrench and Add to Favorites, right? Is it different for some end users? It seems like adding a dialog window would add steps. What access level do the users in question have?

Domo is working on replacing the Governance Datasets, but this has been years in the making. As such, use what is there if it has not yet been created in DomoStats.

@ColemenWilson - I upvoted that baby and commented already. It is SO needed. I actually have a dashboard of all of the issues I have found in the activity log, as well as unclear activity. I provided it to Domo via support, and it went nowhere. (Not Ben's fault. It didn't even get to him. I was trying to use the correct…

@Julianna_Potter - I figured that may be the case! Seeing who it was, I was pretty sure it had to be something like that, but I didn't want to assume.

@Julianna_Potter - Do an export of the dataset before you take action if it's not too big to do so!

I assume he's going to build it as a pivot table, rather than creating a field for each date. The maintenance on that would be crazy. I also don't think the average will work if there are multiple entries for a particular category per day. You would need an average daily total. I think @DavidChurchman is right, and it's…

I think it's wise for them to not support that capability, since things can go awry very easily. With all of the new capabilities Domo is releasing, you don't even need to build a recursive, so it's pretty nice.

What if it's triggered when the maximum week number changes?

I'd like to staple this answer to my brain!

Can you give a little more of an example of what you are looking for as your final result? Also - this looks like a pivot table.

I have run into this before. Same feedback for cards. It's too easy to delete a card that is in use elsewhere, particularly if you do not have access to the page because it won't show up in your move/copy!

I have seen it, and it is real. It is coming. 🤩

I LOVE this! I think it comes up a LOT! I know that I have sat there, creating way more color rules than seems reasonable, just so that cards are comparable. It's amazing the difference it makes when you can see that a particular categorization is really big here and really small there, for example, but without rules, that…

We need 'Contains' so badly! None of the workarounds work for the use cases I encounter the most.

@cadellfalconer - This is something that should be readily available - probably as a DomoStats Dataset, just like Users and Groups are. I would assume the endpoint has to already exist, since the data populates the org chart UI in Domo. And…of course…it would be brill if this could be used in PDP so that access could be…

It may be helpful to see what that hover looks like and where on the page it is. From what I am gathering, it's on the page, rather than the card, otherwise I would think it may be the card interaction settings. But if it's an app, it may still be that. There are so many places where interactions can be set.

@MichelleH said what I was going to say. It can't handle aggregates of aggregates. I find that putting the sum outside the case logic often solves this issue. Think of your case statement as a filter, and then aggregate the results. I also recommend breaking it apart and reviewing the results of each portion of the beast…

Hi @newbie123 - It's a best practice to only build cards off of datasets which have been through a dataflow, however, I understand that under the new consumption model, that has consequences. So - If we must be building cards off of raw datasets, here's a beast mode that may help you: Date(`Date`) If that doesn't work, you…

Should the Plan be the series instead?

CONCAT('$',`Your_Column`,'B') Though I like Colemen's solution much better. If you use mine instead, please also mark his as a solution, as it's solid.

We have been asking for this quite noisily for YEARS! Some day…SOME DAY! @BenSchein

In case you want to use your beast mode: COUNTDISTINCT(CASE WHEN Reporting Date = '31 December 2023' THEN Client Entity ID END) Obviously, that's not exactly it, given relative dates, etc, but I wanted to give you the order for that type of beast mode in case it helps you.

It's the double sum conundrum. lol

I agree with nulls being the issue, but I would do it in the dataflow. 😉