Data_Devon Contributor

I have noted that this shall be disregarded. Thank you for tending to this matter.

Wooohooooo!!! I couldn't have done it without this community. Onward 🚀

I currently have the allocation table in a wide format - with additional galleys as new columns. and, in the case of John, no additional columns since he just goes to his own galley. Per @ArborRose 's sample table - i'll make this long data instead and add new columns with effective dates. I tried to jimmy rig this logic…

That's exactly what I was thinking - maintaining a BeastMode would be difficult but a reference table would be much easier to maintain as a source of truth. I didn't know I could also reference a separate field(s) in the reference table that would have effective dates. Should be good to go - but I'll keep you guys posted.…

This is exactly the issue! Brent is due/credited/owed half of Kristin's appointments, but since the mapping is one:one (i.e. Justin » John….Mitch » John…..Kristen » Tanner) there's no place for Brent to get credit.

@Cfunk Make sure you have the underlying dataset(s) shared with the App users! That's what fixed this for me.

Still having the same issue so standing by for input from someone

Bump - just had this same issue. Can you confirm that your test user is NOT an Admin? Admins (and Page Owners) can see everything, so PDP won't be applied.

I would use a "Value Mapper" tile for this, like so: Obviously you'll have to change the 1st field to search the relevant column in your dataset. Let me know if this works :)

Amazing!! I've got some FOMO now….. Run it back in October??

We don't have AI enabled on our instance… Any other ideas?

I'd also recommend exploring Apps. They'll be much more robust in terms of design and user flexibility.

Me before: me now:

I think I might understand now. You understand the failure rate of a given state and can create that field as a BeastMode. Once you've created that field as a BeastMode, I recommned using it as a "Tooltip" to display at the State Level. Check out my screen shot below with anotations included: Use the "Data label settings"…

I don't fully understand what you are after, but hopefully we can get you there. You should be able to just use the native "Map" chart type. This will get you a map of California (or whatever) with each county displaying the value it has.

🐐🐐🐐🐐

Hi Roman K! Yes, you can do exactly this using the drill path settings from a card options menu. Click the Wrench > Edit Drill Path > and click "Prevent Drilling to final data…." If this becomes cumbersome, then I'd recommend digging into PDP or custom roles as you mentioned. But for single cards, this is the way 🌠

Given the forum you're asking this on, I think you already know the answer :) I (not speaking on behalf of VTV here) like Domo for these reasons: it's NOT Microsoft Nimble, deployable, and cloud-native Thriving community Amazing support, documentation, and knowledge base It's not microsoft That's just me. I'm sure others…

Hi Ritesh! It looks like you have it sorted by Alphabetically even though the X-Axis is a date type. Click the little "ZA Arrow" sort button on the Y Axis, as shown in my screenshot, to toggle through different sort options. One of the sort options will be by date, as you are intending. Doing it this way, you won't need…

Wooohooo!! When's the GOAT reaction coming??? 🐐🐐🐐🐐

@Kyrsten - Thank you! I don't know how the colors got added… It seems like it was just a default coloring that Domo applied automatically. I thought perhaps it was the "Entry" or "Exit" indicator in the Chart Properties, but that's something else entirely. None of the other Chart Properties have it as an option either, so…

Oh boy. I've been struggling with this too for a while. There's a few really good write ups to get you started, so I won't claim to know the answer but rather point to those who do: https://community-forums.domo.com/main/discussion/53481/a-more-flexible-way-to-do-period-over-period-comparisons#latest…

He must be much nicer than his profile picture would suggest! /s

@ColemenWilson is 🐐🐐🐐 so either of these solutions should work for you John_LARM

In my experience, the CASE WHEN statement has been the single most useful argument I've used for BeastModes. To solve your question, I'd do something like this: COUNT(CASE WHEN `Widgets` = 'Purple' THEN 1 ELSE 0) — the CASE WHEN argument looks at your `Widgets` column and returns a 1 if it's purple. You then count all…

Amazing!! That's exactly what I'm doing and exactly the problem I ran into. Thank you @DavidChurchman and @GrantSmith for getting me where I needed to go. I appreciate this community a ton!

I like that @DavidChurchman - and that's closer to what I'm currently doing. I'm forcing a wide dataset by BeastMode-ing the "Last Year" records into their own columns. The only difference is that I also BeastMode the current year into wide format, thus rendering dates useless. I think you provided the best solution…

Awesome, thank you @GrantSmith . I think we are getting close. The flexibility of using the dynamic "CURDATE()" instead of hardcoding a date value is awesome. In order to use the native "Choose Date" & "Graph By" filter that is native to each dashboard, I need to include the Date as the X Axis: I think we're getting…

Thank you @GrantSmith ! I may have misunderstood your write up, but all the solutions you shared are for when you have one value but multiple periods assigned to the value. I have the opposite problem - 1 date with multiple values assigned (budget and actual) Did I misunderstand your write up?

Option 4 will be the only solution here, since filter cards work on the dataset that they are powered off of. Since the "Custom" dataset and the "Daily" dataset are different, then the two cards (the table card and the filter card) won't interact as expected. As such, the root issue in your challenge is creating a join…