Stupid question (and Iâm kicking myself for not picking up on this when we did that bit of scripting the other day), but why do you have a separate column for every single payment option?
Wouldnât it make more sense to write whatever payment option is selected into a single âPayment Optionâ column?
Also, itâs not clear from your video - which sheet is your form adding a row to? Is it the one that the PDF is generated from?
And Iâm not sure about Jeff, but Iâm still struggling to get my head around exactly what it is that youâre trying to achieveâŚ
It is just what the client wanted. I think itâs silly myself too.
Yes, it is that one.
So let me explain this project. The whole purpose of this PDF is to generate a cover sheet that then goes on top of the stack or bundle of paperwork that each dealer independent dealer faxes to finance companies. This cover sheet contains the basic sale information once a demo has been completed and the product has been sold.
For the immediate problem at hand, can you describe what the user experience should be?
eg. Once they submit the form, whatâs the next thing you want them to see?
It runs that logic within the action then I put on submit. Allowing the system to take that value in that select and upon inserting this new role writing to the appropriate field based on that value.
Okay, I think the penny just dropped for me. The root of your problem is those multiple columns for payment option and the fact that you can only target the choice component at a single column. Fix that, and your problem goes away.
Yes?
Yes. 
I was seriously over complicating this thing.
I wonât argue with that 