It'll take a little bit of tweaking on your part to get it right - but I would suggest making a formula text object in Quickbase that builds a 'json' string that you can have direct control of in an easier to use format. Basically you can have a bunch of if() statement for if( part 45 is present and qty > 0 then build json. Your json object should look something like:
"data": [
...REPEAT FOR EACH FIELD
{
"fid of part field": {"value": "part value"},
"fid of qty field": {"value": "qty value"},
"fid of related parent record field": {"value": "record ID of something"}
}
]
You would do that for each field first checking if it has a value and if it doesn't then ignore that entirely.
You'd then want to build a pipeline that does a Request using the REST API and specifically the insert/update records call
The reason for the above is that if you have upwards of 50 fields and quantities, if you try and do an add record for each the pipeline will max out with the 26 steps available right now. You could try and do the above purely in the Pipeline - but it'll be almost impossible to read and hard to manage. In this example, putting it in native QB first allows you to actually see the payload and you know its right/accurate and then the Pipeline is basically just a passthrough to load.
