Data_Devon Contributor

Starting a new thread @ArborRose I got the Overhead by just making a separate branch and then joining it back to the main dataset. Good to go! I think the last little piece of the puzzle is this: Since Overhead is calculated on each line (Grouped by Location, Plan/Budget, and Accounting Period) - the YTD Overhead is…

Thanks for the good videos. I'm not sure why but my mind really struggles to understand the logic under these aggreagtions. I just can't get the "why" to click and the lightbulb to go off

You're right it's a formula tile. Using a Group By tile instead, I was able to get the Aggregation, but now I lost all the other columns/rows I need. If I add those columns back, then I lose the Operating Overhead column (because some of those columns have a 0/null value) I think we are very close but just need to get this…

Yes, I have a DEBUG output. All of the Operating Overhead column outputs a null or a zero, because either the Total Expenses column is populated, or the Gross Profit column is populated - but never both. As such, the Operating Overhead has a zero in either the numerator or the denominator - both cases not helpful. I tried…

@ArborRose - thanks a ton. I especially appreciated the example. It's like "under the hood" of an Excel Pivot table? I got the Group By's built out for the aggregated financial accounts (the rest of the CASE WHEN is correct): And then used the "Add Formula" tile to do additional math on other summary financial accounts:…

Do you agree with this setup?

I have the accounts flagged with a "END AS" in the SQL tile, and then I math those with some calculate tiles. The calculate tile won't allow a division though - which is what I need for overhead since it's a percentage. Sounds like I'll have to Group By. I haven't worked with those a ton so this'll be fun learning.…

Amazing. I've had to learn the hard way to "under promise and over deliver". I too often OVER promise and get myself stuck.

Congrats Kronk! and Congrats to ArborRose. The 🐐🐐🐐GOAT remains undefeated.

Can't wait to see everyone IRL!! I heard @ArborRose isn't actually a viking IRL 😱

Hi Luke! You can accomplish this through the "Hover Legend" chart properties, by changing the "Position" to "Inside", as such: Chart Properties > Hover Legend > Position > Inside

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??? 🐐🐐🐐🐐