Forum Discussion

WilliamLatimer's avatar
WilliamLatimer
Qrew Cadet
7 years ago

How to update a default (canned) report with a custom field?

I am using a QuickBase app I downloaded from a list of suggested PM apps. It contains quite a few canned reports. Is there a way I can can add a custom field as a filter? In the current list of filters offered,  when in edit mode, it only offers original fields, no custom fields I have added to the app are listed as an option to select.
reports and charts

13 Replies

Sort By
  • JustinTorrence1's avatar
    JustinTorrence1
    Qrew Member
    7 years ago
    I think you are talking about Dynamic Filters? (The Element on the left sidebar of a report that allows you to filter data on the fly) There is a section in the report builder called "Filters", and a subsection in there called "Dynamic". Switch the radio button to "Custom" and you can select all of your own Dynamic Filters. Some fields cannot be used as a dynamic filter. There is a chart at the bottom of this page that shows you what kind of fields can be used as a dynamic filter: https://help.quickbase.com/user-assistance/dynamic_filters.html

  • AviSikenporePro's avatar
    AviSikenporePro
    Qrew Trainee
    7 years ago
    The custom field also needs to have the property checked that says - include this field when searching/filtering this table. This should then allow you to use as a filter in any report.


  • WilliamLatimer's avatar
    WilliamLatimer
    Qrew Cadet
    7 years ago
    Thanks for the replies.  To be more specific, I am trying to change the search parameters of the report to return records for the logged in user, where the custom field (ETL Lead) is equal to the logged in user.  In other words, my users are "ETL Leads" with projects assigned to each of them and I want "my open projects" report to display their respective projects.  The issue is 'ETL Lead' is a custom field I added.  


  • QuickBaseCoachD's avatar
    QuickBaseCoachD
    Qrew Captain
    7 years ago
    Two solutions because you can�t use a formula on a report builder.


    1. Make a field called [Current User] with a formula of User()


    2. in a report you can match to


    _curuser_


    With those underscores.
  • AlexCertificati's avatar
    AlexCertificati
    Qrew Cadet
    7 years ago
    Well, if ETL Lead is a user field, the easy native solution is to set that value in Filters > Initial. Quick Base provides 'current user' as a standard option in the first dropdown there.



    If it's not, and it's not realistic to convert it to a user field, Coach has your answer.
    • WilliamLatimer's avatar
      WilliamLatimer
      Qrew Cadet
      7 years ago
      No, ETL Lead is a custom field I have added to the app.  When creating a project record, user picks the ETL Lead name from a dropdown list.  If the ETL Lead value matched the actual user value that QuickBase is using via SSO, then I would be fine, but that is not the case.  And its too late now to change the ETL values because they would not propogate to all of the existing project records i.e. the old value would still be present.

      So... I am going to use option 1 that was suggested above and simply create a "current user" field which will always be set to the QuickBase current user value.
    • AlexCertificati's avatar
      AlexCertificati
      Qrew Cadet
      7 years ago
      I basically realized partway through writing my answer that based on the options it was giving you for initial filters in the screenshot that you took, I could see that the easy answer was not going to work. But I couldn't waste those keystrokes!

      There are definitely options to get this figured out, but one way or another you're going to need a 'helper field'.
  • WilliamLatimer's avatar
    WilliamLatimer
    Qrew Cadet
    7 years ago
    Ugh!  Both options result in all records being returned in the report.  My problem is that the values in the dropdown list for "ETL Lead" do not match the values displayed for '_curuser_' .  So when a user logs in the app, the report can't match the _curuser_ value to the corresponding ETL Lead value - they are not equal.  If I change the drop down values to match the _curuser_ values, it only applies to new records.