Jump to content

Search the Community

Showing results for tags 'sql contact importer'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Hornbill Platform and Applications
    • OpenForWork
    • Announcements
    • Blog Article Discussions
    • General Non-Product Discussions
    • Application Beta Program
    • Collaboration
    • Employee Portal
    • Service Manager
    • IT Operations Management
    • Project Manager
    • Supplier Manager
    • Customer Manager
    • Document Manager
    • Timesheet Manager
    • Live Chat
    • Board Manager
    • Mobile Apps
    • System Administration
    • Integration Connectors, API & Webhooks
    • Performance Analytics
    • Hornbill Switch On & Implementation Questions
  • About the Forum
    • Announcements
    • Suggestions and Feedback
    • Problems and Questions
  • Gamers Club's Games
  • Gamers Club's LFT

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start








Website URL





Found 5 results

  1. Could the SQL Importer be extended to give a reason/warning in the log when skipping or failing to process a contact record. This way it would be easier to locate those updates which have not been able to be applied. The only way to locate them at the moment is page through the log file and look for the single line. Also, when the tool errors can the text just be a normal colour rather than red on black which is quite hard to read. I have tried changing the command prompt to change the default background colour, but to no avail as the tool sets both the background and foreground colours for the error message output. Cheers Martyn
  2. Can the SQL Contact Importer be updated to support all the h_sys_contact fields to include the h_tel_3 and h_email_3 fields added in the platform updates in 2018. Cheers Martyn
  3. We are attempting to use the SQL Contact Importer to load the contacts for next service desk we are going live with on the Hornbill platform, but the Hornbill SQL Contact Importer is failing to connect to our source MySQL 8.0 database due to the version of the MySQL due to the version of the go-sql-driver used in the tool. Can the SQL Contact Importer be updated to use the newer driver please. Reference https://www.pixelstech.net/article/1531316568-Fix-this-authentication-plugin-is-not-supported-issue-while-using-Go-to-connect-MySQL-8 Thanks Martyn
  4. I just run the process of bulk loading in 784 contact records which from my data matching are all new contacts. Running the same data and configuration dry run mode reports 784 processed. Running it again non dry run mode to process the contacts, it reports 777 records updated non skipped. Given that the contacts did not exist in the database before hand and now do with my API Key name user as the creator etc, why is the log reporting them as Updated rather than created. Also it does not seem to be reporting properly what happened to 7 other records either. Is there a problem with the logging logic on the importer? Cheers Martyn
  5. When loading bulk contacts you can specify the logon_id, but you cannot specify a contact's password or indicate if their guest portal account should be created and whether it should be Approved or Suspended. https://wiki.hornbill.com/index.php/SQL_Contact_Import Can the tool be extended to include these facilities, so it will make migrating customers from previous systems more seamless. Cheers Martyn
  • Create New...