Forum Discussion
My best guess is that since you're not including the QB Key as a field to export then it's can't properly map. So in your 'Source Table Export Fields', add your 'QB Key' field so that QB is actually pulling that field. When you do that - there should be another input value that asks you to map that column, so you'll map it to the QB Key field again so that QB is matching key to key to update the same record(s)
------------------------------
Chayce Duncan
------------------------------
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
------------------------------
- Yurij7 months agoQrew Member
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
------------------------------ - ChayceDuncan7 months agoQrew Captain
I'm not sure I follow - did you change the key field of your connected table? You don't need to - Record ID# is unique for QB and so it will allow you to properly merge with no issue and has no affect on the actual key field of the table. It's just a way for QB to make sure it's updating the right record so long as they field you're using is unique.
------------------------------
Chayce Duncan
------------------------------ - Yurij7 months agoQrew Member
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
------------------------------ - ChayceDuncan7 months agoQrew Captain
You shouldn't need a trigger - the idea would be to just schedule the Pipeline to run on a schedule so the very first step of your pipeline should be the query. The idea is that this should run immediately after your connected table. So lets say you have your connected table running every day at 8AM - then you would schedule the pipeline to query and process these records at 8:30AM for example.
------------------------------
Chayce Duncan
------------------------------ - Yurij7 months agoQrew Member
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
------------------------------