Jump to content

Recommended Posts

  • 1 month later...
Posted

Our User import tool does such: https://github.com/hornbill/user-import-database & documentation: https://docs.hornbill.com/data-imports-guide/users/database/overview

To be fair, the CSV import works via an ODBC connection. There is a to-do item on the dev list to remove that extra step, but, as the ODBC-route currently works, the priority of this to-do item is low. Either way, any changes there would only affect the source configuration and probably not the mapping.

Posted
On 16/05/2024 at 15:34, SamS said:

Our User import tool does such: https://github.com/hornbill/user-import-database & documentation: https://docs.hornbill.com/data-imports-guide/users/database/overview

To be fair, the CSV import works via an ODBC connection. There is a to-do item on the dev list to remove that extra step, but, as the ODBC-route currently works, the priority of this to-do item is low. Either way, any changes there would only affect the source configuration and probably not the mapping.

Sorry not sure if I am missing something but I can't see anything on the docs that mentions using a csv file? I just see Database, Entry ID, Google Workspace or LDAP?

Posted

Hi @will.good,

CSV falls under Database in this instance. The connection goes via ODBC.

As stated, native CSV is on the "ToDo"-list to add, but not anytime in the near future.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...