ContributionsMost RecentMost LikesSolutionsRe: Table Relationships - Connected CSV Table Hi Chayce, Unfortunately, the upstream process to produce the connected table data is not rigid and the refresh will need to be done manually. We'll have to simply run the pipeline manually as well if the trigger can't be hooked by the refresh table manual action. I appreciate all your guidance in resolving the issue. ------------------------------ Yurij ------------------------------ Re: Table Relationships - Connected CSV Table Hi Chayce, Yes I changed the connected table key field from QB Key to Record ID#. The refresh key of the connected table is still the QB Key. This way I was able to select the Record ID# as the Merge field. I'm not sure why this works but on a hunch I suspected the pipeline didn't like the connected QB Key read-only key field. After I modified the Merge field it didn't work until I added the Record ID# field to copy/paste from Source to Destination. I'm now stuck on adding a pipeline trigger. I was hoping that once the Refresh data is manually clicked the records would be modified, added or deleted (as expected) and the pipeline trigger would work. It seems like a user needs to modify, add or delete in order to trigger the pipeline. ------------------------------ Yurij ------------------------------ Re: Table Relationships - Connected CSV Table Hi Chayce, The connected table key field was the same as the Refresh Key "QB Key". I modified it to be the Record ID# and then changed the Merge Field in Pipelines to Record ID#. As you suggested, I also sent the Record ID# field from the source table and mapped it back to itself in the destination table. The copy was completed but now I'm not sure if the connected table will like a different table Key. Thoughts? ------------------------------ Yurij ------------------------------ Re: Table Relationships - Connected CSV Table Hi Chayce, I tried as you suggested but because the table is a connected table, it seems I can't overwrite any "connected" fields such as the QB Key. The only options I have to map are Record ID and the Related Order which I'm already mapping the Lookup Order Record ID. Any other thoughts/suggestions? ------------------------------ Yurij ------------------------------ Re: Table Relationships - Connected CSV Table Hi Chayce, I'm back at this and I tried running a simple pipeline that copies the formula numeric query field Lookup Order Record ID to the same table Related Order field. Unfortunately, the field values did not copy over. Looking for your help here. I used the Quickbase channel - Copy Records as follows: What am I doing wrong here? Perhaps there's another Pipeline function I should use? Thanks for the help! ------------------------------ Yurij ------------------------------ Re: Table Relationships - Connected CSV Table Looks like I spoke to soon and got the following message when I tried to create additional summary fields. Looks like QB doesn't like this. ------------------------------ Yurij ------------------------------ Re: Table Relationships - Connected CSV Table Hi Chayce, Here's where I ended up and it seems to be working. I created a formula numeric field 'Lookup Order Record ID' and used the query you suggested to lookup the Parent table Record IDs based on the Child table Order field. It worked like a charm. I then modified the Related Order field type created by the relationship from Numeric to Formula Numeric. In the formula I simply pointed it to the Lookup Order Record ID field. The summary fields in the Parent are now populating. Let me know if this approach is not recommended or if it should be okay. Thanks for your help! ------------------------------ Yurij ------------------------------ Re: Table Relationships - Connected CSV Table Hi Chayce, Thinking out aloud here again. Can I simply create a formula field in the Parent and use query to lookup and sum up the fields from the Child? If this is an option what i is the downfall? ------------------------------ Yurij ------------------------------ Re: Table Relationships - Connected CSV Table Hi Chayce, Thanks for the reply. I feared this may be more complex and I was hoping to avoid "2-way " data uploads. That being said I haven't used the Pipelines or Table to Table imports functions but will educate myself further to see if this automation is doable for day to day users. That being said, is there perhaps any way to create a Third table in Quickbase (ie. Join Table) that summarizes the Order field and via formula populates the Parent Record ID. Then the Third Table is related to the Parent Order table via that record ID? Brainstorming here. Maybe its not possible. Thanks! ------------------------------ Yurij ------------------------------ Table Relationships - Connected CSV Table Hello Community, I'm relatively new to QB and hoping this is an easy one for someone. Background: Parent Table - Orders Child Table - Actuals Relationship One-To-Many Orders -> Actuals The Child table (Actuals) is a timecard export (csv) from our enterprise software that I plan to update periodically using manual refresh as part of the Connected Table functionality. The child table has many timecard entries for several orders. Ultimately, I'd like to create a report from the Parent table that summarizes fields from the Child table. eg. Sum of JTD Hours related by the Order #. So, I've created a relationship between the two tables and added summary fields to the parent table. When I run the report and use the summary field in the report the data is blank. After reading several discussions I've played around with Reference IDs, Keys, Proxy fields, formulas pointing to other fields, join tables but I haven't been successful. From what I gather the relationship isn't established properly but I can't figure out why? So, I'm starting fresh, hopefully with the help of this community. I'm sure I'm missing something super basic here. Here's a snapshot of the simplified table relationship where I've stripped it down only to one target Summary FieldTotal Sum of JTD Hours although there are several in reality. I'm hoping someone can step me through this. Note the following: A text field Orderexists in the connected child table that identically matches theOrder # field in the parent table. Order # is a formula text field in the Parent table that essentially concatenates several fields in the Parent table. Appreciate any help I can get on this. Please advise if more information required. Sample Table Data Parent Table Report with Order # field and Target Summary field Total Sum of JTD Child table report with QB Key field, Order field and Sum of JTD Hours ------------------------------ Yurij ------------------------------