Best Of
Re: New Guy Here - What's the Point of Apps??
Additionally, here is some more information until then:
Dashboards visualize data to answer business questions. They make data consumable for anyone.
Apps not only enhance your visual experience with data but also let you operationalize that data and make it more actionable with a lot of flexibility to customize and curate your own branded experience quickly. With the first release of App Studio’s no code apps we introduced custom navigation, branding, themes. New components such as tabs, spacers and action oriented features such as buttons, page drills, persistent filters, workflows, queues etc. All this with full mobile support!
With App Studio, you can place a lot of your content within a single hood as it allows you to package multiple pages within a single viewing full screen experience. Tabs allow you to group and visualize your content better by adding contextual reference with grouping and allowing you to best utilize your space. The navigation within the apps are fully customizable with icons, headers, landing page of your choice, etc. While you move between these different pages, persistent filters allow filters to stick globally within the app with specific column selections as well!
Themes allow you to quickly switch between different Domo curated themes that apply across different components with ease. Fonts, custom chart palettes, card styles, borders, spacing, padding, rounded corners, drop shadows and so much more for every component type to elevate your visual experience! It also lets you apply your company brand colors without having to spend a lot of time applying those selections to every component separately.
You can utilize buttons, workflows, forms and queue widget to drive actions. Buttons can be used as navigational tools to create a custom landing page that connects to different parts of an app or to drill into a full new details page view or for card and form pop ups. You can use it to perform even simple actions like clearing filters without having to jump into your filter panels every time. We are planning to continue to add more actions to the button in future.
Along with this, we are fully integrated with pro code apps, bricks and other elements to allow you to embed custom apps within your no code creations.
We are continuing to add more features and customizations to App studio.
Some of the upcoming big features include a custom Report Builder which is currently under development and it will allow you to create custom curated reports with different pages of your app for reporting purposes. This is slated to go out to Beta in Jan 2025!
We’re also introducing new App Component types to help you view and drive action directly from your app along with smaller enhancements in App Studio all along the way!
Re: Move multiple cards from 1 tab to another tab in the same App?
While you can't move tabs, you can use the multi select feature to move multiple cards at once from your page to another page. Use Command + Click on Mac or Windows + Click on Windows to select the cards and use the Add to option to add these cards to the app pages/dashboards of your choice at once.
Re: Weather Data
@Glory711 There are a few NOAA weather connectors in the app store. I'd suggest checking those out to see if they give you what you need.
Re: How to migrate Workbench jobs to new server safely?
The last time I utilized the backup and import backup, it created new jobs with the same definition but with new datasets and job IDs, which caused a lot of issues and duplicated datasets.
What I recommend doing is doing a registry migration where it treats the new server as the existing server and Domo will restore all the jobs as is. You'd just need to make sure you don't have them both running at the same time.
Here's some documentation on this process:
GA4 Connector Settings Best Practices
Those of us who work with Google Analytics 4 data understand getting the data to accurately pull into Domo is at best tricky and really does take closely studying the settings and creating ETLs. I thought it would be a good idea to collect our best practices in one place.
For example, if you want to get an accurate user count over a period of time, you really need to be pulling separate datasets for every possible period of time. It's not a perfect solution (we can't get an accurate count of users for a two-week period, or a quarter), but it will get you most of the way there. So make sure you set up separate datasets for users by:
Day
Week
Month
Year
You could include sessions in this dataset as well, but if you're okay with your data being slightly off (a session might span two days), users really is the most critical and most noticeable part.
Re: Input DataSet - Load New data
I can't see why only some of the tiles are displaying the error from what you've said and shown, but I can say that upsert DataSets don't support data version filtering.
Most DataSets (Replace and Append DataSets, excluding upsert) are loaded into Magic ETL in the form of a list of the originally uploaded files (usually CSV though sometimes other formats). Version filtering works by selecting a subset of those files to load, rather than loading all of them.
However, upsert DataSets are exposed to Magic ETL in the same way as DataSet Views. That is, the DataSet is exported from a database in its entirety. This exported table does not contain information to determine which rows belonged to which uploads. In the case of Views it's not clear how it ever could (since every row could be the product of any number of upstream tables), while in the case of upserts all we can say is that it does not. Currently.
I hope to see this limitation relaxed in the future. If you want to dig into the reason for the missing error messages on the other 8 of your inputs, feel free to DM me.
Re: Need help writing a Beastmode
The formula as Grant has typed it looks correct. Assuming your typing exactly matches the condition logic.
Using a fake dataset:
hospital_name | current_balance | financial_class | aging_group |
---|---|---|---|
Central Hospital | 15000 | Medicare | 0-30 days |
Central Hospital | 22000 | Medicare | 31-60 days |
Westside Clinic | 5000 | Medicaid | 61-90 days |
Eastside General | 30000 | Private | 91-120 days |
Eastside General | 10000 | Medicare | 121-180 days |
Westside Clinic | 7000 | Private | 181-270 days |
Central Hospital | 4000 | Medicaid | 271-365 days |
Central Hospital | 8000 | Private | 366-730 days |
Eastside General | 1500 | Medicare | 731+ days |
Westside Clinic | 32000 | Medicaid | 0-30 days |
Eastside General | 24000 | Private | 31-60 days |
Central Hospital | 2000 | Medicare | 61-90 days |
Westside Clinic | 4500 | Private | 91-120 days |
Eastside General | 21000 | Medicaid | 121-180 days |
Central Hospital | 17000 | Medicare | 181-270 days |
Eastside General | 14000 | Medicaid | 271-365 days |
Westside Clinic | 11000 | Private | 366-730 days |
Central Hospital | 27000 | Medicare | 731+ days |
If I throw this on a pivot table and try to guess at what you have on yours.
and also throw the test calculation at the end to see if it calculates correctly…it is aggregating the proper values that I show highlighted in yellow.