I'm trying to streamline some manual processes, and running into inconsistent results.

I'm importing data into a child table. It has 4 snapshot fields that are set from the parent record.

The child data is coming from a 3rd party, cleaned up (ex. making sure parent record id is correct). The goal is to get the clean up out of Excel, and simplify the upload to the child table.

The fields on the parent record used for the snapshots are based on summary data from the child table. Specifically - based on the type of visit, if the Minimum visit date = Maximum visit date, then the child record being added must be new. It is the "new flag" that is used for the snapshot on the child record. FWIW - as weird as it sounds, yes the summary fields do appear to account for the new record as it is being added.

I've moved the clean up to a worktable in Quickbase, no problem.

I wanted to use pipeline to move the final data from the worktable to the Child Visit table.

I created the pipeline, (simple API_RunImport) ran it, but only 34 of the expected 245 records had the correct snapshot values. Bummer. Reviewing the lookup fields on the parent & child, the values were correct. Just the snapshot wasn't set correctly.

I cleared the data, and manually ran the defined TableToTable import. This time only 3 of the expected 245 records had the snapshot set correctly. Bummer again, going in the wrong direction.

I cleared the data again, downloaded the data to CSV, then manually did Import from CSV.

This time I got 234 out of 245 records set properly. The ones that were incorrect, I could possibly account for. The child table has 4 different snapshot fields, related to different types of visits. If a parent record client had 2 types of new visits, there would be 2 records in the dataset. Only 1 would have the new snap field properly set. The other would not. I'm guessing it probably has to do with QB caching parent record data. I could solve this by separating imports by visit type.

Does anyone have a suggestion on how to get the pipeline to add records with correct snapshot values?

I would consider this a bug, but would like to know what the community experience is with snapshots and data imports.

For those wondering about repeat visits, I have those separated out, and they would be a different import, just to prevent issues with the New visit calculations.

thanks,

------------------------------
Andrea Best
------------------------------

Forum Discussion

Snapshot fields and Importing records

Snapshot Fields

Snapshot calculations

Merge Imports

Qrew Tip: Calculations per Record

Pipeline to add Parent record from child import