Method Community

I am using the MethodAPIUpdateV2 to update fields in the Customer table. All of the fields that I am attempting to update are fields that I added, I am not trying to update the CustomerName or FullName fields. Occasionally I get the error "Save Warning: The Customer/Employee/Vendor/OtherName could not be sent to QuickBooks.  This Name is already in use.  Please edit the Name so that it is unique and save again."

Why would I be getting this error if I am not trying to change the name at all?

Hi Matt,

You are getting this error when you are modifying a customer that has the same value for a parameter "Name" as other Customer/Employee/Vendor in the database. This shouldn't normally be the case, since "Name" field is usually a unique field, but it does happen in exceptional cases. Since you are not modifying the "Name" field, you should not be getting this message even if you do have duplicate name values. Our developer team has fixed the code and now you should not be having the same problem. Sorry for any inconvenience this might have caused.

Thank you

Victor

Hi Victor,

I tied it again last night and I'm still getting the same message occasionally.

With the change to the code, what should happen if there is a duplicate name? Should it now be saving the update?

Hi Matt,

In order to have a better resolution to your problem, can you give me an example of a query you would do with a MethodAPIUpdateV2?

With a change of code if there is a duplicate name, but you are not editing the name field itself, then you should not be getting any error messages and the record will be updated with data you had passed in.

So for example if we have two customers with name "Mike":

Scenario 1 (This will FAIL and will not update the values): MethodAPIUpdateV2(strCompanyAccount, strLogin, strPassword, strSessionID, "Customer", "Name", "Mike", 12)
Scenario 2 (This will PASS and update the values): MethodAPIUpdateV2(strCompanyAccount, strLogin, strPassword, strSessionID, "Customer", "AccountNumber", "777", 12)

Hi Victor,

What I am doing is exactly like scenario 2. I am updating multiple fields that are all custom fields, so none of them could possibly be the name field. If it would help, we could do a GoToMeeting for you to see it in action. I have some time on Thursday morning. Let me know if that would help or if I can provide any more information.

Thanks

Hello Matt, I've introduced one more change to MethodAPIUpdateV2. If that still doesn't help, then I will be happy to help you through GoToMeeting on Thursday. Thank you Victor

That seems to have done the trick. Thank you very much.