Aaron_Trent Member

Haha, I started the thread 3 months ago. I can pinpoint the time of error to between 4:45PM and 5PM on 2026-09-15 as I was actively creating a new ETL with a SQL window function.

Hi, has there been any progress on this feature? It is available in dashboards and is very important to have in App Studio.

Just one more agent, bro.

My ETLs are running again, thanks!

Yes, this is happening in SQL tiles with window functions for me.

I also get the sense that Domo has diverted resources to AI at the expense of the core product. At this point Editable tables are not stable enough to use for testing and are a feature my org has identified as vital.

The functionality I am looking for is this: A business user would like to filter a table of invoices with many thousands of unique invoices. They would like to see 50 or 100 at one time, preferably by pasting a comma separated list into a search bar and selecting all that remain. I'm not sure from your response if your…

Is it in a Pro Code App or App Studio?

This is a much needed feature. Our business users do not have edit rights and cannot create calculated columns. A filter that allows a field to be filtered on a comma separated list would enhance usability for business users and reduce the small, unimportant work power users would need to do to create a one-off beast mode.

@GrantStowell I see that you have accepted an answer for this question, however, that answer didn't solve the issue. The post I am replying to is the correct answer. I'm not sure of the etiquette regarding accepting my own answer.

It's a bar chart.

I was able to resolve this by changing the dashboard level time scale from Default to Day. Still seems odd to coerce a date field to time as a default setting.

It has been resolved for us!

I was able to restore functionality by sharing the forms data set with the business users. Documentation claims this is unnecessary, but as of Friday morning I believe this is incorrect.

Please refer to this accepted answer to see the resolution. https://community-forums.domo.com/main/discussion/comment/103145?utm_source=community-share#Comment_103145

I had not, but that fixed it.

Thanks, the details link sent me to the same dead end. I have submitted a support ticket.

When I responded Arbor Rose' response wasn't visible. That suggestion seems like the better option.

You could use DATEDIFF(minute, Created Time, Response Time) This will return the number of minutes between Creation and Response. If you want to exclude non-working hours you might need to use a master calendar with a field like date start time and date end time with work start and end time for every day and use the sum of…

We are happy with the speed gains for a first pass. I'm also testing out the idea of only processing the multi-item entries in Magic and the single entries in Views. I'm currently fighting with Window functions in Views. Single entries make up about half of all user inputs. I am comfortable in both R and Py but this…

I checked and the max number of selections so far has been 80. I did add a pre-processing step in the morning that handles all old entries. This allows my main ETL to only need to import form entries from today. ETL time has dropped from 40-45 seconds to 18-20. This is better, but still not as performant as using Views.…

The users sees a table with appx. 25,000 unique items, where Item is the key. The most recent non null value for Vendor, Status is joined to that table for each Item.

Thanks, I am going to submit this as an idea.

@ggenovese I am accepting this answer. It's a bit clunky compared to the filter cards but this seems like a Domo limitation.