The only tables you will find that field accessible in will be JobRecurringInstance (orders) and RecurringOrder (which is the order definition for creating recurring invoices). AutoCharge cannot be changed on any other tables and does not exist on the standard Job and Invoice tables.
Again, is this actually resulting in recurring charges or are you just “not liking” that it’s set to yes?
If you’re not creating subscriptions then I’m not sure a record (row) will exist for the order on those tables. You may just be seeing a “default” setting that shows when it’s not set.
@John_Borelli I do not found any record in RecurringOrder table and i am not create any subscription. I will check the default setting and let you know.
I’m afraid you’re trying to approach this from a “I want this so there is a way” thinking. The AutoCharge value just simply does not exist if you are not creating subscriptions. If you were creating subscriptions then the recurring tables already mentioned would be your only options; but that does not apply here. The ‘yes’ you are seeing is an interface element set to yes when the value doesn’t exist. You’re not going to be able to change it. Besides, you’re spending way to much time on something that has no effect (at least if your time is valuable to you)
If you’re not creating subscriptions then there is nothing to auto charge. But since it’s a concern for you, setup a test case and see it in action for yourself.
Why my import to IS is slow? Can you suggest how can i improve speeds.
See my script working below
check promotionalDiscount zero then proceed
check custom fields for contact if exists then update user otherwise insert.
update /add user with custom fields
check custom fields for product if exists then update product otherwise insert.
add/update products
check invoice id from job for updating records within single order other wise create new order with record and retrieve job id again for inserting custom fields for job.
I don’t see code you mention and I don’t know enough information to answer. However, you would do well to keep logs so you can track the responses coming back from api calls.
Add up the number of api calls being made. While they are relatively quick, yes, the authentication for each call, the lookup or writing data and then returning back to the caller x number of times? Sure that can take a bit. Think about all the check if this exists and update and creates you mention…every one of them is an api call for one contact…You will also be wise to check to see if you aren’t getting throttled for using calls too quickly.