Method:Classic General Q&A

Re: Entity Duplicate Conflicts

Method_Adam — Tue, 27 Nov 2012 14:48:45 GMT

Hi Mark,

I heard back from the dev team. They are aware of this. We try our best to match Quickbooks logic when accepting a save and passing on to Quickbooks. In this instance, despite our best efforts, the conflict is created. There is no resolution or fix at this time.

- Adam

Re: Entity Duplicate Conflicts

Method_Adam — Mon, 26 Nov 2012 22:26:10 GMT

Hi Mark,

I was able to create the conflict. I'll put this into our dev team and update this thread. Thanks.

- Adam

Entity Duplicate Conflicts

LaCrews — Mon, 26 Nov 2012 20:17:03 GMT

I don't know if this is a known issue but there is a common conflict that is generated due to a duplicate entity.

Method will show a warning if you attempt to save a duplicate entity. For example, if a customer named "Practice Test" already exists in Method and you attempt to enter a new customer named "Practice Test", method will show the warning the same as QuickBooks.

The problem is, if a customer named "Practice Test" already exists in Method and you enter a new customer named "Test, Practice" (or vice versa), method accepts this but a conflict is created because QuickBooks sees this as a duplicate customer/entity. The problem is then compounded because the Method user can then use this customer to create invoices, work orders, etc. When the conflict is resolved typically by deleting the duplicate the existing invoices, work orders, etc are orphaned.