samwoo

Nice idea!!! +1

Please add me +1

Thank you very much, i've had success with using entityUpdateRecord.

Thank you, that makes a lot of sense. Can I be added to said story? Cheers, Samuel

Thanks again Trevor, i am still getting this issue after defining the "acqMethod" 1, it's now producing the same error but this time for the next parameter, actualRetireDate. Many thanks, Samuel EDIT: Interestingly, when defining the actualRetireDate = "2999-01-01 00:00:00" I run the script again, and still get the same error message, but this time for a field further down the table.... cost. So it doesn't seem to happen for every field one after the other. Also these fields are not mandatory in the Computer Asset Class on Hornbill.

Thank you for that Trevor. I've gotten further now. Write-host "$h_asset_number" Write-Host "`tAsset ID:`t$h_asset_id" Write-Host "`t" Write-Host "`tSerial Number" Write-Host "`t`tChange: $h_asset_serial_number ===> $serialNumber" Write-Host "`t" Add-Param "assetId" $h_asset_id Add-Param "name" $h_asset_number Add-Param "type" $h_asset_type Add-Param "version" "1" Add-Param "serialNumber" $serialNumber # Invoke XMLMC call, output returned as PSObject $xmlmcUpdate = Invoke-XMLMC "apps/com.hornbill.servicemanager/AssetsComputer" "updateAssetComputer" if($xmlmcUpdate.status -eq "ok") { Write-Host -ForegroundColor Green "Success! Asset updated in Hornbill" } else { Write-Host -ForegroundColor Red "FAILED!" # API call status not OK - return status and error to console "API Call Status : " + $xmlmcUpdate.status "Error Returned : " + $xmlmcUpdate.error } I am still new to this sort of thing so apologies in advance... now i've got a different message: Error Returned : FlowCode Exception (com.hornbill.servicemanager/entities/AssetsComputer/fc_ops/updateAssetComputer): nodeName: Invoke Flowcode: Update Asset; nodeId: #######-####-####-## ##-############; At 152/1: "Uncaught EspMethodCall::invoke: Operation[apps/com.hornbill.servicemanager/Asset::updateAsset] FlowCode Exception (com.hornbill.servicemanager/entities/Asset/fc_ ops/updateAsset): Input parameter validation error: Non-digit characters found in the element <acqMethod>, the expected data type is 'integer'. The value was [undefined] at location '/metho dCall/params/acqMethod'" throw(e); _fc_node_exec_#######_####_####_## ##_############ It states that the field acqMethod is optional on the api page... do I still have to include this and the other optional fields in my query until I get all the way up to the SerialNumber field? Thanks, Samuel

Hello, I am trying to update some assets in Hornbill from a spreadsheet. In particular i am trying to insert/update the Serial Numbers where they don't match in Hornbill on the spreadsheet. The first things I do in the script (which works) is import the contents of the spreadsheet into PowerShell, then loop through each of the rows and check the corresponding record in Hornbill. If there is no match, then this should run: Write-host "$h_asset_number" Write-Host "`tAsset ID:`t$h_asset_id" Write-Host "`t" Write-Host "`tSerial Number" Write-Host "`t`tChange: $h_asset_serial_number ===> $serialNumber" Write-Host "`t" Add-Param "application" "com.hornbill.servicemanager" Add-Param "entity" "AssetsComputer" Open-Element "searchFilter" Add-Param "assetId" "$h_asset_id" Close-Element "searchFilter" Add-Param "serialNumber" "$serialNumber" # Invoke XMLMC call, output returned as PSObject $xmlmcUpdate = Invoke-XMLMC "apps/com.hornbill.servicemanager/AssetsComputer" "updateAssetComputer" if($xmlmcUpdate.status -eq "ok") { Write-Host -ForegroundColor Green "Success! Asset updated in Hornbill" } else { Write-Host -ForegroundColor Red "FAILED!" # API call status not OK - return status and error to console "API Call Status : " + $xmlmcUpdate.status "Error Returned : " + $xmlmcUpdate.error } ($h_asset_id is the asset number found in the previous invoke-xmlc which compares the serial number from the spreadsheet to Hornbill and returns if there is no match) No matter what I do, i cannot seem to get the Hornbill record to be updated. Everything works instead of where i am trying to invoke-XMLC. I get the following error message with this version of the script: FAILED! API Call Status : fail Error Returned : FlowCode Exception (com.hornbill.servicemanager/entities/AssetsComputer/fc_ops/updateAssetComputer): Input parameter validation error: The element <application> was not ex pected at location '/methodCall/params/application' Can someone assist? This may be just a silly little thing i've missed out. Thanks, Samuel

Sounds interesting - please add me to the change. Thanks.

Can I be added as well please +1

Hi @TrevorKillick, Thanks for getting back in touch. Please disregard this post. I changed the details in the LDAP Import configuration on Hornbill and saved it (and it went greyed out) but I just went back into it and it didn't save. I set the values, then moved to a different room then saved it... so it must have been a connection hiccup or something but it's working now. Many thanks, Samuel

Hello, We are currently using LDAP_Import 2.0 and we have a need to start using LDAP_Import 3.0 to be set to import over SSL, do we need to store the SSL certificate in Hornbill? If so how? Using the standard HTTP connection and LDAP_Import 3.0 with Dry run enabled, it works... we then tried to configure it to SSL and doing a dry run it's producing the following error: [ERROR] Bind Error: LDAP Result Code 211 "ErrorClosing": Response Channel Closed Can you advise? Thanks, Samuel

Thanks Daniel

And me +1

Hi @Daniel Dekel, Many thanks! Samuel

Thanks @Daniel Dekel, Is it ok to ask for an ETA on the next Portal build? Just an approximate timescale for the Service Desk to be aware of. No worries about the colour for the time being, but as an outcome of your response, can this be raised as an enhancement request please Many thanks, Samuel

Hello, When users log a ticket via the Self Service portal, the mandatory fields are not clear until they press next. Can I request this to be added in a matter of urgency? I swear there used to be a red bar on the left hand side of the field to indicate this... and I remember users not finding that clear enough to determine whether the field is mandatory or not. Users are attempting to fill out the forms and not knowing what fields they need to populate causing them frustration when pressing next, and we have been getting more complaints about it. Ideally if we could have the fields to be highlighted in a colour of our choice if Mandatory, that would be great. (such as a "Mint" green colour, "Sunshower Yellow" colour or even a nice "Celeste" blue colour) Thanks, Samuel

No, but i've recently gotten Horizon Zero Dawn and love it (i'm a bit behind times i know). What is God of War like?

Hey @NeilWJ - I can see the screenshots now, thanks! Looks good too, am looking forward to putting this to use as will save a lot of time.

Hi @TrevorKillick, It's currently set to "Single Level". Here are some screenshots to show what I mean: PowerShell: Active Directory Export: Hornbill Log: Hornbill Data Import Configuration: I can also confirm that the batch file is using the correct config name: Thanks, Samuel

Hi @TrevorKillick the info you provided has been helpful thanks. Just a quick one, I am trying to import from an OU, single level. Doing a count in this OU using PowerShell returns 45 accounts. Exporting from AD into Excel is also showing 45 accounts... but the log file for the LDAP_Import says this: Shouldn't this be saying "45" accounts?: I have doubled checked the OU path in PowerShell, Hornbill and the location I am looking at in AD and it is the same. Maybe I am misunderstanding the message about how many Accounts of Processed? Thanks, Samuel

That is correct. How bizarre!

@NeilWJ - Your screenshots have disappeared into Oblivion :'(

agreed +1

+1 from us aswell! Another idea is to be able to raise a request related to their assets.

Hello, I wold like to request for there to be more information on the Wiki regarding LDAP 3.0 As of current the Wiki isn't fully up to date with regards to the new feature so am struggling to find answers. In the meantime can someone answer the following for me: 1. In the LDAP Server tab - what does the "Types only" box do? 2. In the User Account tab, what do we put in for the Time Zone and Date Formats and the other similar fields? 3. In the User Options tab what is the "Member Of" field in the Organisations region and how does this differ from the "Value" field? Many thanks, Samuel