SimonSheldon Posted July 1, 2019 Share Posted July 1, 2019 I'm using the LDAP Importer to import users from AD ... on the User Options section it adds them to our company and a cost centre. The cost centres generally exist in the organisation section already - and if it does it exist then the user is added to the correct one, however if a new cost centre is created in our accounts systems this isn't automatically created in Hornbill when the LDAP import runs. In our old Supportworks system we had the cost centre import run as a separate process before the users were imported - would I need to have the same happen in Hornbill with a separate LDAP import scheduled to run before the main user import? I have this set on the user import at the minute: Link to comment Share on other sites More sharing options...
SimonSheldon Posted July 15, 2019 Author Share Posted July 15, 2019 Bump for this one? Link to comment Share on other sites More sharing options...
Steve G Posted July 15, 2019 Share Posted July 15, 2019 Hi @SimonSheldon, The LDAP import tool won't currently import new cost centre records if a match is not found. Are these cost centres just in your LDAP, or are they stored seperately in your accounts system too? The reason I ask is that we're in the process of writing an import tool for group type records (so cost centres, departments, teams etc) which could be pointed at a database or ODBC data source of your choice, that could be scheduled to regularly import any new cost centre records in to Hornbill. Cheers, Steve 1 Link to comment Share on other sites More sharing options...
SimonSheldon Posted July 16, 2019 Author Share Posted July 16, 2019 Thanks Steve - That sounds like just the ticket - similar to what we used to have in Supportworks then? They are in AD but also in our accounts system - which is Oracle DB based - and also held in a SQL Database which would probably be the preferred option. Link to comment Share on other sites More sharing options...
Steve G Posted July 16, 2019 Share Posted July 16, 2019 @SimonSheldon Yeah exactly, import your cost centres then follow it up directly with your user import. SQL would be the preferred option for us, the tool already supports SQL Server, MySQL, MariaDB and ODBC. I'll give @Victor a nudge to get it released, as he's the one who's been writing it Cheers, Steve 1 Link to comment Share on other sites More sharing options...
SimonSheldon Posted July 16, 2019 Author Share Posted July 16, 2019 excellent - thanks for that again Steve - would be most useful! Link to comment Share on other sites More sharing options...
Victor Posted July 16, 2019 Share Posted July 16, 2019 I'll try and have it ready by next week 1 Link to comment Share on other sites More sharing options...
SimonSheldon Posted July 16, 2019 Author Share Posted July 16, 2019 even better! thanks @Victor Link to comment Share on other sites More sharing options...
Victor Posted July 26, 2019 Share Posted July 26, 2019 @SimonSheldon - apologies, I had to delay the release of the import tool. There are only a few bits to iron out so I hope to have it ready soon. Link to comment Share on other sites More sharing options...
SimonSheldon Posted July 29, 2019 Author Share Posted July 29, 2019 no problem - thanks Victor! Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now