- JotForm SupportKevin_GAnswered on February 22, 2017 at 04:17 PM
This seems to be happening only when you edit your form in the v4 builder, if you edit the form in our v3 builder it will work fine and the custom invoice number will be indeed passed to Authorize.net without any problem so in the meantime I would suggest you to make changes on your payment field through our v3 builder.
I will also forward this to our second level so this issue can be resolved.
We'll let you know as soon as we get any update regarding this.
- SunbridgeInstituteAnswered on February 23, 2017 at 12:10 PM
Would I have to convert all of my forms over to version 3, and then leave them in version 3 for this to work? I'm getting a little nervous about all these switches back and forth between 4 and 3, and it's especially disconcerting that it looks like I'm now on version 4 yet my settings say I'm on version 3. See here:
Can you please confirm which version I'm really using, and then can you tell me exactly what I must do to make this custom invoice number pass through to authorize?
Thank you very much.
- JotForm SupportKevin_GAnswered on February 23, 2017 at 01:31 PM
Your account is currently set to work with the v3 builder and if you make the changes in the invoice number field from the v3 builder it should be saved, if you decide to switch to the v4 builder again I would suggest you to avoid making changes on the payment field.
Also, if you need to edit one single form in the different JotForm version than your account is currently set up then you could click on the more button and will find the other builder version at the very bottom.
For example, if your default builder is v4 then you could find the v3 builder as option:
If your default builder is v3 then you should find v4 instead. This switch should not affect your forms, they should work fine if you edit them either in the v3 or v4 builder.
If you have any question, let us know.
- JotForm DeveloperomurAnswered on February 27, 2017 at 07:35 AM
Thank you very much for reporting the problem.
I've issued an update that solves the issue.
It is working as expected now.
Thank you very much