Best Of
Re: prioritize recent data for input datasets in dataflows for preview
I would like to amend this request. Rather than simply prioritizing recent data, as I requested at Domopalooza 2024, I would like the ability to filter the datasets being brought in. Let me hit that 100k row limit based on attributes in the data. This would make dataflows an invaluable tool for tracking down data anomalies and simply understanding the datasets better without having to run the dataflow and check results.
Re: Reverting Back to the old dataset version
This only works if the dataset isn't the output from a dataflow, irrespective of recursion. So basically you can retrieve lost data via the history tab on any raw connector from the appstore, jupyter connectors, workbench connectors, etc.
Also, restoring a dataflow to a previous version and re-running the dataflow only restores lost data if the data loss was a result of the code change and the datasets powering the dataflow had not run/updated since the data loss.
jessdoe
Re: Background Image App studio
I think you can set the background image in the App settings. If you adjust the card transparency on all your cards, the background image may be visible through the cards.
Re: Export on cards with embedded Domo Everywhere App Studio
This feature really needs to be added. Almost no point in migrating our dashboards to apps if users can't export content
Re: How do we keep the changes we make to the people's DOMO name?
Verify if the manual updates are being consistently saved. After saving, review and make sure you see (TRAINER). And make sure you have cleared the cache.
Check for Overwrites
Ensure that there are no processes or integrations that might be overwriting the manually updated names.
Data Synchronization
Confirm that there’s no conflict between your manual updates and any automated synchronization processes.
Permissions and Roles
Double-check that the users performing the manual updates have the appropriate permissions. And check to make sure other users with access, are not overwriting your naming.
Re: Filtered date selection
You could do this using variables and beast modes. You'd need four variables (period 1 start, period 1 end, period 2 start, period 2 end). Then you can create two beast mode to use those those variables to get your sales (eg, period 1 sales could be sum(case when date_field >= period_1_start and date_field < = period_2_start then sales end).
If you need to calculate the difference, you could make a third beast mode subtracting one of your sales beast modes from the other.
Re: How can I make a historical/week over week chart without a provided date field?
You could do a recursion to store values to an archive each week. Then poll the archive to identify changes.
Re: Do new values get swept into an "all" card filter?
If you are selecting all values, is there a reason you would even apply a filter? Because not applying a filter at all would select all values

