Data_Devon Contributor

I tried making the form that was accessible from within the app - but that's what led to the "Error Loading Form" issue! I did just get confirmation from Domo support though that there was a bug in the Form so it is perhaps resolved.

Thank you @MarkSnodgrass for the input :) When you say "make that form in Domo", I assume you mean that I can deploy it from within a normal Dashboard interface?

Anyone? Please 🥹

Shoot - sorry that wasn't the case. Commenting again for reach and visibility. Standing by for the GOATs 🐐🐐🐐

Hello b_rad, In your random date validation, it looks like you typed in the dates. I'm assuming that in the working formula, you will have to reference the column that contains the dates you are trying to find the difference between. For example: DATEDIFF(month,`Start_Date`,`End_Date`) If the error you are getting is about…

Assuming you are looking for all possible chart types, I love referencing @DashboardDude 's recipe book: It helps me see and interact with all the possible chart types. I also really like this chart from MajorDomo training. It's presented as a flow chart so you can help narrow down what you are after:

Your best bet will be a transformation in Magic ETL or through a Beastmode, but it depends on your end goal. If using this while building a card in Analyzer, you can use Beastmode and this code to achieve it: DATE_FORMAT(BIRTH_DATE,'%m/%d/%Y') If you can access Magic ETL, then you'll just use that same formula above within…

When users attempt to access their App, they get this error I suspect its something to do with the Form that is in the App since they can access the app but the Form (which is the only thing in the App) doesn't appear. I have a ticket out to Domo Support, too.

Any updates? I'm experiencing the same issue.

Hello caiorogano! Why would the sales remain constant even if products are removed? Also - what is your relationship between the datasets assuming that Salesperson is your Join Key? Is there one row per Salesperson, and values/area of operation/products are pivoted out to new rows? I want to make sure I understand before I…

Hopefully the GOATs 🐐 can chime in, but here's what I'd do: Use this CASE WHEN (you were on the right track thinking of using the CASE WHEN) to flag a date as before today: CASE WHEN `Date_Time_Start` < CURDATE() THEN 'Older' ELSE 'Newer' END This will create a new column that can signify whether the date is for a past…

Yin Fire Ox 🔥🔥🔥🔥 That was wayyy too much fun @DashboardDude 😂

Thanks to @DashboardDude 's help, I got exactly where I needed to go: I had to move away from a PoP chart and do a standard Bar Line Chart. Here's the BeastMode that did it: CASE WHEN YEAR(`Date`) = (YEAR(CURDATE()) - 1) — this allows us to look at last year (a peculiar problem since the new year just churned — and we are…

Current Year Actual, Last Year Actual, and Budget :) There's lots of TLAs in this industry (three letter acronyms) Bummer on changing the name on the legend - but I think your second answer could work. I'll just need to get away from the PoP charts and use a time-agnostic chart like multi-line or bar charts.

I agree with Manasi_Panov. PDP should be the most efficient way to handle the access rules: PDP Knowledge Base

Ours is pretty straight forward - basically just a "front door" to Domo with minimal options. This will be a fun thread to follow to hopefully revamp ours:

🐐🐐🐐🐐 Thank you! (we need a new reaction for the GOATs)

@ColemenWilson - yes, I've got dates and times. That should do the trick - but there won't be a set rule for the pre-procedure events. I.e. It could be any number of things that happen before an upgraded procedure, so there won't be a rule that standardizes it. Do you think this will be an issue?

I can't figure that one out - so standing by for the GOATs to chime in. 🐐🐐

Hi Connor! Using the Scatter Plot, there's a "Grid lines" chart properties that you can edit: In other chart types (pictured below is the Bar chart), there is the same "Grid lines" in Chart properties that will offer the same adjustments - such as removing the Min and Max line, or removing the calculated line: Does that…

A deep honor!! 🤝 I'd like to thank my dog for always encouraging me, my ergonomic mouse with side-scroll functionality that lets me easily get to the 329th column, and my team for their outlandish requests that always require new skills to be obtained in Domo. Onward!! ⛷️⛷️⛷️⛷️

Hi hollyrene1225. Have you looked into the "Period over Period" chart types? They are mostly plug and play, so you wouldn't need to do any cooking in Magic ETL - just select the chart and you are off to the races. You could also look at a bar chart with a line added - again, mostly plug and play. Is that what you are…

Thank you Dashboard Dude! Loved the video. Unfortunately, neither of those is exactly what my Project Manager is after so I'll have to break the bad news to him.

You can use the "Filter Rows" tile in Magic ETL to get rid of rows that you don't need.

That is a normal pivot added by the upload process to provide helpful Meta data on the underlying dataset - so you didn't do anything wrong! To ensure your ETL still runs as expected - throw a "Select Columns" tile prior to the transforms (upstream) and remove those 2 metadata columns.

Hi Kim_Barragan! You can retain those extra columns within the Group By ETL tile that GrantSmith mentioned. Just "Add All Columns" in Step 1 of that Group By tile, or select the specific columns that you mentioned. This should retain the columns you need downstream, but also create the group by that you were originally…

Hello, and welcome to the community! I trust you'll feel supported and encouraged as you delve into the Domosphere. I like to use "Filters" card types that are placed in a logical space around the table that will reflect the applied filters. The "Dropdown selector" will be perfect for your use case. You can create a table,…

Thank you both for the theory and the practicality in this.

@DashboardDude - that'd be awesome. I love your content and I always use your "data as ingredients" analogy.

There isn't a native solution for this as you are explaining it. However, using any filter card, the filter label would update and be descriptive of the reporting period filter. There are other work arounds within Beastmodes or Magic ETL, but again, I don't think it's exactly what you are after unfortunately. Did I…