opensynchelp

Recommendations

Info

OpenSync The EditSequence field is used by QuickBooks to insure updates made within QB do not get overwritten by updates from OpenSync. Every time a record is updated in QB, the EditSequence field is incremented. If an update is attempted and the EditSequence fields do not match, OpenSync will fail the update with messgase indicating the EditSequence values do not match. Although not recommended, this behavior can be overridden by setting the EditSequence field to NULL. This will overwrite any data in QB with the data from the database. Update Conflicts Update Conflicts Created with the Personal Edition of HelpNDoc: Write eBooks for the Kindle QuickBooks is always considerd the database of record. If a record is updated in QuickBooks and the same record is marked for updating by OpenSync, the OpenSync update will fail. This lgoic is implemented using the column named EditSequence. Every time a record is updated in QuickBooks this field is incremented. When OpenSync attempts to update a record in QuickBooks the EditSequence field from the database is compared to that in QucikBooks. If the numbers do not match, the update will fail. Although it is not recommended, you can override this update check by setting the EditSequence column to null in the database. Update Errors Update Errors Created with the Personal Edition of HelpNDoc: Easily create PDF Help documents All errors that occur durring an update process are loged in the error_table. This table can be accessed from the Error Table tab in the database status window as shown below. 48 / 66
OpenSync Fields included are: Err_Num - an numeric identifier for the error Error_Table - the table the error was detected in Error_Filed - the field within the table that caused the error Error_Desc - a description of the error IDKEY - The ListID or TxnID of the record that caused the error Entities Created with the Personal Edition of HelpNDoc: Full-featured Kindle eBooks generator Processing Entities Entites in QuickBooks consist of Customers, Employees, Other Names, and Vendors. When adding entities you must be sure to populate the Name field regardless of the entity you are trying to add. If the name already exists in QuickBooks an error will be returned. Customers Customer Created with the Personal Edition of HelpNDoc: Free help authoring tool If you wish to add a "job" or a "sub-level" customer you must add the full name of the parent in the ParentRef_FullName field. For example, if you want to add a job named MyJob under the customer name Synergration, you would place 'MyJob' in the Name field and 'Synergration' in the ParentRef_FullName field. If you would like to add a job to a preexisting job then you include the customer and the parent job in the ParentRef_FullName field seperated by colons. For example if you wanted to add a job named 'Part- A' to the previously created job MyJob, then you would insert 'Part-A' in the Name field and 'Synergration:MyJob' in the ParentRef_FullName field. The same logic applies to Items. Customers also provide custom field support and the ability to rename the customer. Supported Fields -Customer Table AccountNumber AltContact AltPhone BillAddress Fields CompanyName Contact CreditCardAddress (QB 2003 or greater) CreditCardNumber (QB 2003 or greater) ExpirationMonth (QB 2003 or greater) ExpirationYear (QB 2003 or greater) NameOnCard (QB 2003 or greater) CreditCardPostal (QB 2003 or greater) Email Fax FirstName IsActive JobDesc JobEndDate JobProjectedEndDate JobStartDate ListID (Required) 49 / 66
Page 1 and 2: OpenSync Copyright © 2013 by Syner
Page 3 and 4: OpenSync Updating QuickBooks ......
Page 5 and 6: OpenSync Starting OpenSync Add a Co
Page 7 and 8: OpenSync The OpenSync screen uses t
Page 9 and 10: OpenSync Select the location and na
Page 11 and 12: OpenSync On this screen, you should
Page 13 and 14: OpenSync Now you need to tell OpenS
Page 15 and 16: OpenSync Run a Task Run a Task Task
Page 17 and 18: OpenSync Task Status The task statu
Page 19 and 20: OpenSync If you are using the trial
Page 21 and 22: OpenSync Adding a company file Addi
Page 23 and 24: OpenSync To add a database for use
Page 25 and 26: OpenSync Oracle The final step in a
Page 27 and 28: OpenSync The database status screen
Page 29 and 30: OpenSync Refresh Report operations
Page 31 and 32: OpenSync The final step in adding a
Page 33 and 34: OpenSync Running a Task Tasks can b
Page 35 and 36: OpenSync Task Status The task statu
Page 37 and 38: OpenSync Information - Provides gen
Page 39 and 40: OpenSync The OpenSync background se
Page 41 and 42: OpenSync The browser screen consist
Page 43 and 44: OpenSync Although the default schem
Page 45 and 46: OpenSync Custom field defeinitions
Page 47: OpenSync This status display indica
Page 51 and 52: OpenSync Phone Contact OtherNameAdd
Page 53 and 54: OpenSync Supported Fields -ItemNonI
Page 55 and 56: OpenSync Processing Transactions Th
Page 57 and 58: OpenSync Amount Class ListID or Ful
Page 59 and 60: OpenSync Estimates Estimate Memo Pa
Page 61 and 62: OpenSync IDKEY (Required) - Links t
Page 63 and 64: OpenSync -SalesOrderLineDetail Tabl
Page 65 and 66: OpenSync Vendor ListID or FullName

opensynchelp

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?