Mark Priest

nope havent fixed it

Have fixed this sorry it was an error with the time format on the Azure import

Hi we have recently noticed that our date is out by 4 years in hornbill when tickets are raised and also when we try and change the Time zone on a user profile we get this error

I have the Azure import working to update hornbill with new users, departments etc. I cant seem to get the manager field to update. Have tried different combinations but it is the only part that fails. Anyone else had this issue or can help please. this is what I have been using in the json file "Manager": { "Action": "Both", "AzField": "userPrincipalName", "HornbillUniqueColumn": "h_user_id" },

@Steve G Managed to get this working thanks !

I seem to have the Azure import working however it overwrites the usertype to basic on an existing user that usertype has been changed to user

Hi @Steve G thanks for that info we do already have a group there that all staff are in eg hornbill access. However if users in hornbill already exist will they be over written. In the past with the LDAP import we included all our AD OUs except the IT and other Hornbill full user accounts. Can we exclude Groups from the azure import such as IT or HR in the way we used to exclude people from imports by certain OUs in Active directory.

Hi We are currently testing the Azure import. Is there a way to exclude OUs in the import as in the past with the LDAP imports it has sometimes over written the access for our service desk team and changed their permission to basic user. We dont want this to change the service desk team to user when it does an update. Or am I correct in thinking that it will skip existing accounts and only update departments etc ? thanks

Hi we are getting some users today getting an error Unable to load instance configuration data when they open the hornbill portal before they get to the login screen. Im sure ive seen this before but cannot remember the fix if any thanks

Hi We have a separate service on our hornbill service manager that required separate SLAs to the main corporate ones we use for everything else. Since this has been in use we have noticed that all our services linked to the corporate SLA no longer show response and resolution times, but the service specific one does. If we create service specific for the other services then they also show response and resolution times. If I remove the service specific one then add the linked corporate one to it we still dont get timers until we revert back to the Service specific. Has anyone any ideas as i dont really want to go through all our services re doing all the sla's and rules thanks

Please ignore this I have resolved the issue seems to be with some custom SLAs that were set up

Hi We have noticed that the response times and resolution times for our tickets have stopped working and running. Has something changed or been updated? It used to work fine on all our tickets until the recent issue with Xmlmc method invocation failed for BPM updating service level occurred and the update rolled out. HAs anyone else experienced this as it is throwing out our MI reports to the business we cannot also report on the response and resolve times

@Victor Sorry didnt read that was just excited about testing the new format. thanks

How do you manually raise a ticket from the Hornbill mailbox there is no option to any more on the preview version ?

yep same problem here.