OpenSync

Home Forums OpenSync Updating customer to a sub-customer (job) TO QuickBooks

This topic contains 14 replies, has 4 voices, and was last updated by  Yudel Rosales 1 year, 2 months ago.

Viewing 15 posts - 1 through 15 (of 15 total)
  • Author
    Posts
  • #64225

    LessPaperCo
    Participant

    We have OpenSync connected to a remote MySQL server and we’re trying to get the ability to create customers/update customers working properly.

    Specifically trying to get a customer to be a child. On the child we’ve tried setting ParentRef_ListID and ParentRef_FullName both individually and together and every time OpenSync connects to sync them it just overwrites all the data without actually updating the customer to be a child of the parent. Updating other information (ie, email) correctly sends that information over but the parentref will not stick.

    Are we setting these fields incorrectly?

    #64255

    Yudel Rosales
    Keymaster

    Which version of OpenSync are you using? Are you setting the STATUS field to UPDATE? the running an update task?

    #64257

    LessPaperCo
    Participant

    Most recent version, yes I set the status field to UPDATE and ran the task. It “updates” and I get a new TimeModified but it removes the ParentRef_ListID and ParentRef_FullName and sets the sublevel back to 0 again automatically.

    Not a huge deal – just told my client that they can’t do that and, since it isn’t need often, it won’t be too big of a deal for them to do it through QuickBooks.

    I also noticed that the UserData field does not work as intended – I saw that other posts said the same thing and nothing has been done to fix it yet which is disheartening and the primary reason I decided to start purchasing this for our clients (one right now, two others over the next couple of months, countless more in the future). Now we have to try and link things in a rigged way but it works until that starts working.

    #64258

    Yudel Rosales
    Keymaster

    We are working on it. Sorry for the inconveniences about UserData field.

    #64259

    LessPaperCo
    Participant

    Thank you!

    #64784

    spestillo
    Participant

    Did the issue with the UserData field ever get resolved?

    #64823

    Yudel Rosales
    Keymaster

    UserData field is not supported yet by OpenSync. Sorry for the inconveniences.

    #64876

    spestillo
    Participant

    You really should update your website then.

    Attachments:
    You must be logged in to view attached files.
    #66461

    HM21
    Participant

    Did the Update of Customers as “Child” (sub-customers) work? I have the same requirement and am unable to get it working.

    #66465

    Yudel Rosales
    Keymaster

    Are you getting any error?

    #66470

    HM21
    Participant

    No error, but the ParentRef_ListID and ParentRef_FullName fields are set back to null, also the sublevel is set back to 0 and when I check in QB the customer is not made a sub-customer. However, changes to other fields (for e.g. address phone etc) do get updated which means the update works but for some reason entries in ParentRef_ListID and sublevel fields are just not being processed correctly. Am I missing something?
    The goal is to be able to update a customer to make it a sub-customer of another existing customer record. The equivalent of what you would manually do in QB by right-clicking on a customer entry, selecting “Add/Edit Multiple Customer Jobs” and then in column titled “Job OF:” selecting another existing customer, which effectively makes this customer a sub-customer of the one selected.

    #66485

    HM21
    Participant

    Any updates regarding this issue?

    #66486

    LessPaperCo
    Participant

    @Saifuddin – This was never fixed since my initial complaint – instead I have just been developing our software to not allow customers to be changed from a sub to not a sub anymore. And I just tell our clients that they have to do this in QB if it’s something that needs to be done.

    #66488

    HM21
    Participant

    @LessPaperCo – Thanks for your reply. I was hoping that this would be fixed by now. Will have to work around it then. I would still like to hear from support if they have any plans for fixing this. Seems to me it should be fairly easy to fix in code.

    #66552

    Yudel Rosales
    Keymaster

    Unfortunately, we don’t that have the functionality implemented. Sorry for the inconvenience.

Viewing 15 posts - 1 through 15 (of 15 total)

You must be logged in to reply to this topic.