Forum Discussion

StuLamden1's avatar
StuLamden1
Qrew Member
8 months ago

Issue with Record Picker > Based on Report

Hello Everyone!

I am experiencing a very odd issue that I'm hoping someone can give me direction on.  This was working prior to today and nothing appears to have changed, so I'm a bit confused.  My attachment includes screenshots that should help.

In the table Laptop/Desktop Inventory, I have created a custom report called Computer is not assigned to an employee.

The table only includes 3 records.

The logic behind this report includes one filter.

All of these conditions are true

Computer is Assigned? is not equal to checked.

Computer is Assigned? is a checkbox summary field associated with the Parent Table – Laptop/Desktop Inventory.  The child table in the relationship is the Laptop Desktop Usage.

When I create a new Laptop Desktop Usage Record, I'm presented with the Add Laptop Desktop Usage Record Form.

When I select the Computer – Inventory dropdown on this form, I'm presented with the results of the Computer is not assigned to an employee Table.  I've set this up through the Form Element Settings > Select using record picker > Based on Report > Computer is not assigned to an employee.

So far so good!

Lets says I select the Latitude 9876 and Save.

If I go back to the Computer is not assigned to an employee Table and refresh, you see that the table now only includes two records, which would be correct, since the Latitude 9876 is assigned to the employee Stu Lamden.

Now let's say I want to associate one of these other computers with Stu Lamden, so I once again launch the Add Laptop Desktop Usage Record Form.

The Computer – Inventory dropdown still lists the Latitude 9876 as a choice.

But if I actually open the Computer is not assigned to an employee Table, the Latitude 9876 is correctly not included.  The only way I can get the dropdown correct is by exiting from my app and re-opening.  Only then does the dropdown show correctly and not include the Latitude 9876.

Do you think this is a bug or am I doing something wrong?

Thank you,

Stu



------------------------------
Stu Lamden
------------------------------

5 Replies

Sort By
  • StuLamden1's avatar
    StuLamden1
    Qrew Member
    8 months ago

    One of my co-workers that's very knowledgeable with Quickbase reviewed my app and believes that this is a bug with the new forms.  I have opened a case with support.  I'll include their response when I receive it.

    Stu



    ------------------------------
    Stu Lamden
    ------------------------------
  • DwightMunson1's avatar
    DwightMunson1
    Qrew Assistant Captain
    8 months ago

    Are you 100% positive that you have that report associated with the record picker in the new form? I had a problem recently that it wouldn't save the report as the picker because of some filtering issue or something. I had to change the report group or change the filter or something.



    ------------------------------
    Dwight Munson
    ------------------------------
    • StuLamden1's avatar
      StuLamden1
      Qrew Member
      8 months ago

      Hi Dwight.

       

      I am 100% sure that the Record Picker is looking at the correct report.  We have a former Quickbase developer that works for our company and he offered to review my app.  He believes that I've configured my app correctly and the issue lies with the new Quickbase forms.  I'll definitely share support's response once I receive it even if that means I'm entirely mistaken.  :)

       

      Stu

       



    • StuLamden1's avatar
      StuLamden1
      Qrew Member
      8 months ago

      A Technician from Quickbase Support connected remotely and saw the issue first hand.  He was also able to reproduce the issue on his end as well in his own app.

       

      There are definitely issues with the new form that Quickbase is still trying to work out. 

       

      The workaround for now is to refresh the page, but he's definitely escalating the issue internally.  My case will remain open until he gets a response back internally.

       

      Thanks,

      Stu

       

       



  • StuLamden1's avatar
    StuLamden1
    Qrew Member
    7 months ago

    It looks like this is a bug, here's the response I received from Technical Support Specialist:

    "Hello Stu!

    Thank you for your patience. Our escalation team was able to determine that this is in fact unintended behavior. This has been documented as a bug, and while there is no set timeline, we have our team working to fix this issue and will update the case once it has been resolved. 

    I would like to leave you with the Bug ID: QBE018548
    Once this issue is resolved you will be updated within the case. You can also keep a lookout for this bug ID in upcoming releases.

    I am going to go ahead and close this case in the meantime.
    If you have any related question in the future feel free to reach out and re-open the case by replying to the case via the support portal.

    Mustafa Abdoh
    QuickBase, Inc. | Technical Support Specialist
    mabdoh@quickbase.com"



    ------------------------------
    Stu Lamden
    ------------------------------