TrevorKillick

No, this is the information i was given to put on the Insights page. Kind Regards Trevor Killick

@clampj It should behave as you were hoping where the Only one group assignment would work per type so a user could be in one team and one department as an example. Can you post a screenshot of the Organisation configuration of the LDAP import as well as copy and past the content of the 'Debug' tab in the LDAP Import configuration please. Kind Regards Trevor Killick

@Lyonel I have raised this internally, i will post back with more information when i get it. Kind Regards Trevor Killick

@MizeelA What do the first three lines of the .R script you are using look like Specifically these three: #Define Instance Details instanceName = "Instance Name Goes Here" instanceZone = "eur" Kind Regards Trevor Killick

@Richard Williams The column h_account_status in h_sys_accounts will be 0 for Active and 2 for Archived. Kind Regards Trevor Killick

GTX 770.... 2013 called and wants it Graphics Card back.

@DeadMeatGF Great, glad thats working now. Will take a look and see if there is anything i can do to prevent this type of issue from occurring again. Kind Regards Trevor Killick

@DeadMeatGF Thanks ok so on the instance the KeySafeId is saved as 0, in the Import Configuration can you set the Authentication to "None" save then refresh and set it back to the LDAP Authentication you created and save again? Its very odd for this to happen as the correct id shows in debug but not in the database. Kind Regards Trevor Killick

@DeadMeatGF So the Role has bene there for a while and we keep it up to date with any additional rights needed to run the imports, i cannot replicate this at all are you ok to share your API Key? This will let me see what your import is doing in the background without doing the import. Kind Regards Trevor Killick

@DeadMeatGF So everything looks configured correctly except on your Instance i can see lots of errors data:entityGetRecord() Method call results: failure Its possible the account associated to the API key doesn't have rights to load the configuration and this is not correctly reflected in the Import Errors, does the associated account have the role 'User Import' ? Kind Regards Trevor Killick

@DeadMeatGF Thank for that, can you copy and paste the JSON output from the Debug tab and ping it over in a PM please. Kind Regards Trevor Killick

@DeadMeatGF Thanks, and the id dev-ldap-import is exactly as it displays in the URL of the configuration? Can you also post the log file content again removing any API Key. Kind Regards Trevor Killick

@DeadMeatGF Can you confirm the command line you are using (with the API Key removed) please. Kind Regards Trevor Killick

@DeadMeatGF Can you post a screen grab of the LDAP Server Tab from the Import Configuration please. Kind Regards Trevor Killick

@NeilWJ @HGrigsby Platform support for expanding variables in the report title as well as the report name used for the file name will be available in next Platform Release, when this is available i will post back hopefully should be the next week or two. Neil is also adding support to the Report Builder User Interface to allow you to set the value of the runtime arguments to a more friendly name, this should be available before the platform release. Kind Regards Trevor Killick

This work has now been completed and service to hornbill.com fully restored. Kind Regards Trevor Killick

Good Morning All, For the next 30 - 40 minutes the hornbill.com website may experience periods of downtime. This is to perform some routine maintenance, no customer instances will be effected by this work however the support webform will be unavailable during this time. An update will be posted here when work is completed. Kind Regards Trevor Killick

@samwoo You shouldn't it appears to be the logic inside the updateAssetComputer API that is calling Asset::updateAsset and passing the acqMethod with undefined. I will let the application team know who can advice further. Kind Regards Trevor Killick

@samwoo It looks like you constructing incorrect XML for the API updateAssetComputer https://api.hornbill.com/apps/com.hornbill.servicemanager/AssetsComputer?op=updateAssetComputer It looks to be a mix of entityUpdateRecord and entityBrowseRecord params you currently have set, the above link shows the input params available for this API and which ones are mandatory. Kind Regards Trevor Killick

@DeadMeatGF Sorry i probably should have posted that the fix for this has gone out. Kind Regards Trevor Killick

Hi @lokent The finer details are yet to be ironed out, we are talking about this internally today in a effort to get development underway ASAP. There will need to be some form of triage at initial contact which would then route the chat session to the required team yes. We will keep this thread updated with further clarification as and when its available. Kind Regards Trevor Killick

@Mike Hibbitt What kind of features regarding Service Manager are you looking to be included in live chat? The next feature on the priority list is going to be Support for Multiple Teams, as soon as we have an update regarding this feature a post will go up on the forum. Kind Regards Trevor Killick

Hi @samwoo Great, glad to hear you got it working. Kind Regards Trevor Killick

@samwoo Can you post a screen grab of the first page of Configuration for the LDAP Import please, also what port is configured against the LDAP Authentication in keysafe? Kind Regards Trevor Killick

@samwoo What Scope have you got set? Accounts Processed is the total number of results from LDAP, you can change the log level to debug and you get some more information in the logs 2018/04/13 15:14:19 [DEBUG] Processing Old Log Files Current Retention Set to: 1 2018/04/13 15:14:19 [DEBUG] Query LDAP For Users 2018/04/13 15:14:19 [DEBUG] Creating LDAP Connection 2018/04/13 15:14:19 [DEBUG] LDAP Results: 96 Kind Regards Trevor Killick