ColemenWilson Coach

There is a form action/element you can add to the App Studio App: Have you tried this? Will this meet your need?

I don't know anything about Javascript but have you considered filtering the data through an ETL/Dataset View to current month data if that is all you need for the DDX brick?

For that I would look at Inline Editor: https://domo-support.domo.com/s/article/360042933754?language=en_US It is not as intuitive/easy to use as Domo's other products/features.

I am confused on how these are duplicates. Are they not separate transactions? For example, one online and one in store in the sample data above? If you want to see total value, why would you want to exclude customers?

Commenting in hopes this gets some attention!

There is an idea that @MichelleH posted last year to provide documentation on activity log events/actions. I would suggest others go upvote! This is a huge need for observability and something that should be a relatively easy lift for Domo. @BenSchein…

I believe you need to recreate it. You could export the existing webform and then copy the data into a new webform. Or copy and paste directly from the existing webform into a new webform.

Okay are each of the lines you provided a separate field you want to use in a visualization? I was thinking it was all criteria for how you want to filter your data

This should get you what you need: https://domo-support.domo.com/s/article/360043038714?language=en_US#:~:text=Navigate%20to%20the%20Configure%20tab,you%20can%20switch%20to%20Append.

A calculated field something like the following: CASE WHEN `Policy status` = 'death claim' AND `Termination date` > `Effective Date` - INTERVAL 2 YEAR AND `Term` = 'sure' AND `RC4` IN('Express','Silver') AND `RC5` IN('Essence','Bronze') THEN 'In' ELSE 'Out' END To give you an exact beastmode I would need more specific…

So are there values in the cells above for those fields?

Double check that "Hide total" is not checked for those fields:

@emmanuelfabre_1 you're welcome! Next time you are in Utah let me know and I'll take you up on that!

I added the data for 2024 you provided above and the ETL I shared produces the correct lag_results values without nulls.

Yes I think this is a bug. We are having the same issue as well. I am going to open a support case with Domo and I can add this link so they see you are having the same issue!

Yes, you can use Dataset Alerts: https://domo-support.domo.com/s/article/360042925994?language=en_US#:~:text=You%20create%20DataSet%20Alerts%20in,been%20created%20on%20this%20DataSet. Let me know if you get stuck setting it up!

My understanding is that you are looking for the final value with in a quarter to be the lagged value shown for each month of the following quarter. Wouldn't that mean the lag_result for 2023-05 and 2023-06 being NULL as well? Here is the solution I came up with:…

Seems pretty straight forward. Domo is giving control over which accounts to retrieve. There are only two options: select which specified accounts you want or retrieve all accounts. It sounds like it may have caused some initial issues for you, but were they resolved? What are you trying to figure out?

The solution is to export the card, not the dashboard. When you export content as a PDF, Powerpoint, Scheduled Report, etc… it creates a static export that you cannot interact with as you can in Domo. For this reason, table cards that have over a certain number of rows will be cut off with no scrolling functionality. If…

The solution is to export the card, not the dashboard. When you export content as a PDF, Powerpoint, Scheduled Report, etc… it creates a static export that you cannot interact with as you can in Domo. For this reason, table cards that have over a certain number of rows will be cut off with no scrolling functionality. If…

Here's what I came up with on how to solve this: https://youtu.be/EnN4zuXVkRI

I knew I'd be dethroned at some point but didn't think it would happen so quick! Nice work @david_cunningham !! Congratulations on the coach status!

I've recorded this video walking through how to do this: https://www.loom.com/share/06479b81c71143f28a503c5081b49e7e?sid=5eba93fa-e6e3-43bb-abc0-4a239d97a2ff Let me know if you have any other questions!

If those are the only letters that will appear in the values of that field you could create a beastmode: CASE WHEN `ItemNumber` LIKE '%A%' OR `ItemNumber` LIKE '%B%' OR `ItemNumber` LIKE '%C%' OR `ItemNumber` LIKE '%P%' THEN 'Out' ELSE 'In' END

This is already possible using Brand Kit. If you don't have brand kit currently, you can reach out to your CSM and they can get it enabled for you.

I believe so, and if it isn't you could sign up for a Domo Freemium account where it would be: https://www.domo.com/start/freemium But here is where to look in your current instance:

Yeah, that is what all users see - the standard default drill path. Your options are to create a custom drill path (as you pointed out), disable drill paths, or keep the default. You could also submit improvements to the default drill view as an idea in the ideas exchange.

Could you provide a screenshot of what you are seeing? Just want to see if it is the same view the rest of us see or something different.

@Chris_Wolman Awesome! I stand corrected!

It could if you have beastmodes saved to the old dataset that are not in the cards/dashboards. But if they are saved on the cards and the fields stay the same, they should still work. Definitely test with 1 ETL before switching them all over!