Best Of
Add Magic ETL Runtime History to History tab
The current magic ETL history page for any particular ETL shows the run successes near the top of the page, in a style that looks similar to a history of git-commits. Hovering over a square shows the number of successful runs on that date. We would like to implement some method of process control visible to all domo users and feel that this space would be a good location to start.
I think that a more useful purpose of this space would be to show the run time history of that ETLs executions as a process control chart. Instead of showing green squares to indicate that date had a successful run, can this instead be a time chart that shows that last n-number of runs and (on the y-axis) show the run time for those runs? Each run can be marked via a point on a trend line, and each point can still be marked red or green for success or failure.
This still allows users to see the same information of run success status, but also provides the run time as a trend over the last n-number of runs. This is helpful to identify ETLs that are starting to uptick in process time, or identify ETLs that happened to take longer than usual.
Attached is an image of a Control Chart that displays the idea behind statistical process control. The x-axis would display the start times of magic ETLs and the y axis would be the execution time. Ideally, we would be able to apply control limits to these charts and set alerts on them, giving us full SPC capability within Domo!
charlieV_OAP
Run Specific Outputs vs All
I would love to see an option when you click run on a MagicETL that there would be a drop down where I can choose to run all the outputs or only specific outputs. This would be an absolute game changer for credit usage and consumption model management. Some of our ETLs have 10 outputs and we are making a small change to one (example, I recently add three columns to one output, that's it) and I had to run it and instead of just running for the one output the ETL now runs for all 10 even though nothing has changed.
Francis
Run History for Snowflake Amplified Connection
Regular Domo datasets will display the run history under the history tab allowing users to see how current the data is and easily see a failure. A dataset created through a Snowflake Amplified Connection does not provide this data. Even though the data is live and displaying what is in Snowflake, we would like to pull Snowflake metadata into this space to easily see when Snowflake last ran, or if it encountered a load error.
One thought to accomplish this is an API where we could publish the history then implement it into the prefect deployment allowing the history tab to update when the Snowflake table updates in a similar fashion as an ODBC dataset
SherryR
Configuration and Scheduling changes of connectors in Activity Log
Currently, the DomoStats Activity Log does not capture records for scheduling or configuration changes regarding connector based datasets. This omission leads to significant visibility gaps, causing users to incorrectly assume that no modifications have occurred when changes have, in fact, been made.
Resolving this issue is essential to maintaining the integrity of the Activity Log. By capturing these specific events, it will help users with a truly comprehensive audit trail, ensuring they can accurately track all configuration and scheduling updates directly within the report.
Ability to hide menu bar
We currently have an instance of Domo where there users should not be able to see native Domo functionality, like the menu bar. Using landing pages we route the users an App Studio app where they can select links to other other apps. While their landing pages load, the Domo menu bar is visible and the users can click on it.
My suggestion is to add a grant where we can choose to hide the menu bar from anyone in that role.
SherryR
New column for Locked and Unlocked Cards/Pages that can be filtered
When we navigate to Admin--> Pages or Cards Tab we want new colum to be added that can allow us to filter based on locked or unlocked. Currently this can be viewd and vaialble as an icon next to Card or page name. But we want it to be available in seperate column which can be filtered.
Make Dynamic Date/Time Functions Respond to the Company Time Zone
The dynamic date and time functions—such as CURRENT_DATE() and NOW()—are represented in UTC, regardless of the Company Time Zone in your Admin Settings. This creates a problem during the hours of the day when the UTC date and your company time zone's dates are unaligned.
For instance, say you have a Beast Mode that uses CURRENT_DATE() - 1 to calculate Yesterday's sales. In Eastern Time (UTC -5), at 7:00pm, UTC changes to the next day. Therefore, the Beast Mode then references the next day (today instead of yesterday), and will show wrong or no data.
Ideally, the dynamic date/time functions should reflect your Company Time Zone rather than UTC. Or this could be an admin setting, like a checkbox that states "Represent dynamic date/time functions in the Company Time Zone". Or there should be two sets of functions, such as CURRENT_DATE() and UTC_CURRENT_DATE().
App Theme Repository / Library
Would be really cool to have a community area to share app themes, if this was accessible directly via the app studio even better!
TC777
Missing authentication events in Activity Log for Domo Platform API (api.domo.com)
I would like authentication events for the Domo Platform API (api.domo.com) to be captured in the DomoStats Activity Log where both the Client ID and the User the Client ID belongs to are captured.
When clients authenticate via the Domo Platform API and exchange the Client ID and Secret for a Session Token, this authentication event does not appear in the DomoStats Activity Log.
The impact of this is that we are unable to monitor which API Clients are authenticating against Domo. This represents a significant governance and security gap for us.