Questions from our June Feature Focus Webinar

Pipelines

1. With the new Pipelines error notification emails can we suppress automatic emails to the Realm Owner/Admins?  
   · Currently there is not a way to pick who among your realm admins receive this email, it will go to all realm admins to assure they are getting notified of technical issues. If this is something you have a need for in your organization, we recommend adding it as product feedback.  
   
   
2. Will the document be saved to a file attachment field? (Pipelines Doc Creation Step)
   · Our Document Creation step for Pipelines has been pulled from this release, we are working on an issue with it that meant we needed to pause on releasing it right now.  
   
   
3. Can we see those templates even if we've built PLs before? (Templates on the new Pipelines Dashboard for users with no Pipelines)
   · Right now, the new Pipelines Dashboard that will show up for users with no Pipelines won’t show up for users with Pipelines, that includes the template Pipelines listed there. You can find some of those same Pipelines in our Exchange listed under the section for Jinja Snippets that can be used to create similar Pipelines and you can also access the help of Smartbuilder to create Pipelines under the AI sparkle that appears in the global bar when you are in Quickbase.  

Grid Reports

1. What is this feature?  
   · We're replacing table reports with the more modern and powerful Grid Reports, which let you directly edit data like in a spreadsheet.  
   
   
2. When will this feature release?  
   · Grid Reports is targeted for open beta in August 2025, but we will provide specific timelines in future release notes 
   
   
3. What plan will have access to Grid Reports? 
   · It will be available on all plans 
   
   
4. In grid edit - will we be able to freeze the first column? 
   · In Grid Reports you will be able to freeze the first column and still be able to edit fields as you move through the report 
   
   
5. Did we get the ability to set the default row height? 
   · The team did add an option for this in the report settings for admins with an eye towards flexibility for end users to be able to adjust it 
   
   
6. When the users adds columns, does it stay (across days? log ins/log outs?), or is it temporary? 
   · Our goal is to simplify the expected behavior for new grid reports from what is currently implemented in current “new style” table reports. We will retain the report state (filtered, sorted, grouped, searched) of the last report the user visited. If you visit another report in the same table or a different table, we will clear the draft state of the previous report.  
   · We will not remember your report state across sessions (log in/log out/timeout).  
   · Report state will also be cleared if you click on the report name from the reports dropdown.  
   
   
7. Word wrap for column height? 
   · We’ll add an option that will allow users to choose if they want to wrap column headers or truncate the values to one line. 
   
   
8. The permission for Grid Report will be only by application, is there an option to enable it by user? 
   · No. The option to enable/disable grid reports exists at the application level. If your users want to continue to use legacy styles, they can switch back to legacy table reports using the “new style” toggle available on the report.  
   
   
9. How many fields in a table have you tested for the column panel? Sadly we have some tables with a LOT of fields.
   · We still need to do performance optimizations for larger field sets but that is something we will be working on during the beta 
   
   
10. How will this impact embedded reports on forms that users grid edit? 
    · Grid Reports will also be available on embedded reports when it is enabled for an app 
    
    
11. Any export option changes 
    · No. Export should continue to work as it does today.  
    
    
12. If you want to limit so they can only grid edit certain fields, but allow users to edit more fields on the detailed form to prevent error updating.  is there anyway to do that?  I know we can do it the other ways that form is more restrictive than the report, but I'm looking it to be the other way. 
    · Custom data validation will be the best option to handle this, though we recognize it’s not a perfect solution.  
    · We are exploring the potential to add in a rules engine for grid reports that would function similarly to forms. Nothing concrete to share yet and this will not be available at the time of launch.  
    
    
13. Will URL buttons work in grid edit? How will copy and paste from Excel into grid edit work? Last question, will you be able to embed grid report in the new form like the old forms and create child records at the same time as creating the parent?
    · Buttons: No, you’ll need to save and use the buttons in view mode.  
    · Copy/paste: Copy/paste should work as long as your columns match in Quickbase to what you have in Excel. Obviously you’ll run into issues if you try to paste text into a date field for ex. Field type data validation is where you might run into issues here.  
    · Create child records in embedded reports: Yes! This will be available.
    
    
14. Are you still able to rename columns/how they display on the report without changing the field name? Changing this setting in current state is pretty cumbersome in that you have to do it in display and can't do it in the report settings.
    · This functionality will still be available. You’ll also still configure them in the same way as you do today on the front of the report.  
    · Overhauling the report builder to include options like this would need to be a separate initiative tackled later.  
    
    
15. Do page down/up buttons work? 
    · Yes, page up/down should be supported. You’ll want to make sure your focus is in a grid cell (select one to highlight it) before you start paging up/down.  
    
    
16. In embedded mode, can you add the add record button to the report?
    · Yes.  
    
    
17. The Column width memory is per user? (Not per report) 
    · It’s per-user, per-report or widget. So if I adjust a column width that will be remembered for me for that report or widget only. It won’t apply for others that are viewing the report, but it will be remembered the next time you come back. 
    
    
18. Are we going to be able to control the columns the users will see? 
    · (I’m assuming this is referring to the columns panel.) The columns that appear here are columns that the user has access to that are marked reportable. Users won’t see columns they don’t have access to.