Re: Parent accounts and adding subaccounts errors/conflicts

Method_Adam — Mon, 31 Mar 2014 17:42:49 GMT

Hi Mike,

This is likely just due to how the SDK accepts new customer records. I believe we handle the entity record slightly differently than QuickBooks and QB has the logic to create a new customer with a value in this field. It then syncs over into Method. I don't believe you need to remove the data already in these fields. You should be fine to leave it.

- Adam

Parent accounts and adding subaccounts errors/conflicts

MikeB — Fri, 28 Mar 2014 19:25:12 GMT

When a new customer (parent) is created, if there is a date in the JobStartDate field I get a conflict saying that this is already a job, and any subaccounts created in Method are not synced in QB. They will only sync if I delete this date value. I follow this logic and it makes sense, as the presence of a value in the JobStartDate field makes QB think that this particular account is a job (when it is not) and you cannot have 2 levels of subaccounts. And yes, I will hide this field and blank it out in our New/Edit account screen in the near future.

But the main problem is, when I export the customer table into Excel and look at all our parent accounts, 95% of them have values in the JobStartDate field, and there are no problems in adding subaccounts.

How is this possible? Should I delete all these existing dates?

Method:Classic General Q&A

Re: Parent accounts and adding subaccounts errors/conflicts

Parent accounts and adding subaccounts errors/conflicts