Discussions

 View Only
Expand all | Collapse all

When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

  • 1.  When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 08:06

    I am trying to import a file into a child table in QuickBase. After importing the data, I am unable to see the relationship between the child record and the corresponding parent record in the parent table.



    ------------------------------
    manohar vankireddy
    ------------------------------


  • 2.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 08:31

    The children will not magically match up with the correct parents on their own.  You need to include the field for Related Country Pipeline in your import.



    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------



  • 3.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 09:05

    But it is not showing while importing



    ------------------------------
    manohar vankireddy
    ------------------------------



  • 4.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 09:10
    Edited by Mark Shnier (Your Quickbase Coach) 03-27-2023 09:42

    I don't understand.  What is not showing during importing? The field for Related Country Pipeline will show.  The lookup fields cannot be populated via an import. They are lookup fields from the Parent Countries Pipeline table.



    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------



  • 5.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 09:52
    Edited by manohar vankireddy 03-27-2023 09:52

    Hi Mark,

    The related field names "Country Pipeline - Study Number" and "Country Pipeline - Country" of the parent table "Country Pipeline" are not appearing while attempting to import data into the child table "Sites Pipeline". Please refer to the attached screenshot for clarification. Can you please provide guidance on how to correct this issue?



    ------------------------------
    manohar vankireddy
    ------------------------------



  • 6.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 09:56

    The field for Related Country Pipeline will show.  That is the field that you need to populate.  The lookup fields cannot be populated via an import. They are lookup fields from the Parent Countries Pipeline table.

    Can you tell me more about the data in the Countries Pipeline table.  What does each record represent.  Is each record the name of a country?



    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------



  • 7.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 10:19
    Edited by manohar vankireddy 03-27-2023 10:27

    Hi Mark,

    The parent countries pipeline should have the following records:

    1. "Study Number" - a numeric value that represents the study. There can be multiple studies in the same table.
    2. "Countries" - the name of the country where the study is conducted. This can have multiple sites in the child sites pipeline table.
    3. "Sites Count" - a numerical value that represents the number of sites in the child sites pipeline table.
    4. "Issues Found" - the number of issues found in the child sites pipeline table.


    Please let me know if anything is required
    ------------------------------
    manohar vankireddy
    ------------------------------



  • 8.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 10:31

    The issue is that when you import data into a child table you also need to populate the "Related Parent" field which contains the Key field of the parent table.

    Currently your Key field of the Parent table is just Record ID. Either you need to find a different key field for that table which can be known at the time of the import, or else you need to do some data manipulation in Excel with your Child table data to somehow calculate what the Key Field is of the parent table before you do the import.  



    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------



  • 9.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 10:43

    Is there a way to automate the population of the "Related Parent" field in the child table with the Record ID of the parent table during data import ? This would ensure that all fields in the related parent table are properly populated without requiring manual data manipulation in Excel.



    ------------------------------
    manohar vankireddy
    ------------------------------



  • 10.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 10:49

    Yes, A pipeline can potentially do this, but it cannot read minds.  So, you would need to be able to describe an algorithm for the  Pipeline to use to calculate which is the correct Parent.



    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------



  • 11.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 11:06

     Could you Please provide me the reference link for pipeline. 

    also I'm going back to previous conversation
    Every time user will import new data into the Child Sites Pipeline table, the "Related Parent" field needs to be populated with the Key field of the parent table, which is currently the Record ID. By doing so, the related field names of the parent table, such as "Country Pipeline - Study Number" and "Country Pipeline - Country", will be displayed when attempting to import data into the child table.



    ------------------------------
    manohar vankireddy
    ------------------------------



  • 12.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-27-2023 11:20

    All I can do is to repeat what I said above.

    The field for Related Country Pipeline will show.  That is the field that you need to populate.  The lookup fields cannot be populated via an import. They are lookup fields from the Parent Countries Pipeline table.



    ------------------------------
    Mark Shnier (Your Quickbase Coach)
    mark.shnier@gmail.com
    ------------------------------



  • 13.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-28-2023 12:14

    It's also possible to manually match up the Parent ID before the import, but that may become bothersome depending on the frequency of your imports. For example, you could export the parent Countries records to a .csv file, where you'd to include the Record ID and some field that is unique (e.g. Country Name). Then, in the child Site records file you intend to import, leverage MS Excel's "vlookup" formula to match Country Name to set the Related Country ID on each Site row before the import.

    Hopefully that makes sense!

    However, if you envision regular imports of child data, I'd suggest a different solution such as sync tables or exploring a Pipelines workflow as Mark mentioned.



    ------------------------------
    Brian Seymour
    ------------------------------



  • 14.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-29-2023 05:26
      |   view attached

    Hi Mark and Brian,

    I'm trying to do update lookup field through pipeline using "Look Up a Record" or "Update Record" both options are not working. I have pasted the YAML code below and attached screenshot

    # Update Country Record
    #

    # Account slugs:
    # - quickbase[aQbv48M]: Pipeline <None>
    ---
    - META:
    name: Update Country Record
    enabled: true
    - TRIGGER quickbase[aQbv48M] record on_create -> a:
    inputs-meta:
    table: '"Customer Sales Activities: Sites Pipeline" <bs6tid8rz>'
    - QUERY quickbase[aQbv48M] record search -> b:
    inputs-meta:
    export_fields: '"Study Number" <6>'
    table: '"Customer Sales Activities: Sites Pipeline" <bs6tid8rz>'
    - b<>LOOP:
    - DO:
    - LOOKUP quickbase[aQbv48M] record look_up -> c:
    inputs-meta:
    table: '"Customer Sales Activities: Sites Pipeline" <bs6tid8rz>'
    export_fields: '"Country Pipeline - Study Number" <12>'
    inputs:
    id: '{{b.id}}'
    ...


    ------------------------------
    manohar vankireddy
    ------------------------------



  • 15.  RE: When importing a file into a child table in QuickBase, the parent lookup fields are not appearing in the import mapping options.

    Posted 03-29-2023 12:21
    Edited by Brian Seymour 03-29-2023 12:24

    Welcome, back to The Mark & Brian Show! Anyone remember that show from back in the day?

    Anyway, in this episode we reiterate what Mark previously stated, you may only import data that "lives in" the destination table. So you may import a "foreign key" (which is stored in the destination table) to re-establish the lookup values.

    For example, in your screenshot you wouldn't be able to import the field labeled "Country" into the Sites Pipeline table (assuming it's really the Country Pipeline - Country lookup that's been relabeled), just as wouldn't be able to edit it on Site Pipeline Form (you'd have to go to the parent Country Pipeline record to edit it).

    But you could import the "Related Country Pipeline" ID (not in your screenshot) into the Pipelines Sites table which would in turn display the looked up values from the Countries Pipeline table.

    Put another way, when using the import feature, if you are hoping to update data in multiple tables, you'd need multiple imports. As you can only import data into one table at a time.


    ------------------------------
    Brian Seymour
    ------------------------------