1 person found this helpful
Is your form inserting the new record using the Built In Automatic Row Processing process?
If so, that's the issue. Your form is saving all the data that was retrieved by the form and the blob is NOT one of those values. That's why you have the pretty links so that the blob doesn't get pushed to the page every time just in case you need it.
So, I think what you need to do is let the new record be created with the Automatic Row Processing process. Just like you do now.
Then have a process that runs right after and updates the new BLOB with the old one. Something like this:
update SBR_PROJECT_DETAILS set bundled_yes_blob_upload = (select bundled_yes_blob_upload from SBR_PROJECT_DETAILS where project_detail_id = :PREVIOUS_RECORD_ID) where project_detail_id = :CURRENT_RECORD_ID;
Tip: Use the Return Key Into Item field in the process to get the new Primary key.
Of course you need to plug in the correct ID values.
Now, important, this process should only run if your BLOB is empty otherwise you would overwrite a possible new BLOB that got uploaded.
Hopefully I understood the logic correctly.
Jorge, that makes perfect sense, I will give it a try! Thank you very much.
Jorge, your post helped me understand the problem but I never actually was able to fix it, due to new requirements taking precidence before I could get a working solution. In the meantime, I found more problems due to the uploaded documents being dropped when the form failed validations for any reason, and having to be uploaded again. I read that the upload process was set up this way for security reasons. I felt this would be a pain for the users, so I separated the uploads from the main form. The users only need to upload their attachments once, even if they create a new version of the form, problem solved. Thank you again.