Steve G

Just to close this off, and in case anyone sees this behaviour in future, the username required the domain specifying. Cheers, Steve

Hi @Berto2002, The error suggests that the account being used to authenticate the requests doesn't have sufficient permissions to retrieve lists of Teams. Note, the above integration has been deprecated and replaced by Microsoft > Teams > Channel > Send Message, which requires significantly less rights that the old integration. There are a number of ways that you can retrieve Teams Group & Channel IDs, the easiest is probably by clicking the ellipses next to a channel in Teams, then Get link to channel, and copying the Channel ID and Group ID straight out of the link that Microsoft provides. You could also use the Get-Team and Get-TeamChannel cmdlets from the Microsoft Teams Powershell Module. Hope this helps, Steve

Hi @AndyHill, This is likely due to the package being updated from the package library on your instance since Wednesday, and your SIS not being updated due to a bug that is now fixed. If you restart the SIS service on the machine running it, it will update to the latest version and your packages will then be able to be downloaded: Thanks, Steve

Hi @AndyHill, We've just released new versions of the Teams Integrations, which use their own keysafe key types and a minimal sets of rights rather than being bundled into the wider Microsoft key permissions: Hope this helps! Steve

@Rob Gething We've just released new versions of the Teams Integrations, which use their own keysafe key types and a minimal sets of rights rather than being bundled into the wider Microsoft key permissions: Hope this helps. Steve

Hi @Paul Alexander, Looks straightforward enough, I'll add it to the list and let you know once we've had chance to look at it. Cheers, Steve

Hi @Berto2002, I had a quick look and it was a 10 minute job, so I added a new operation to do what you need: The existing Post To Channel integration will now return the ID of the newly created message, and this ID can then be fed into the Message ID input of the new Reply To Channel Post integration, basic example: This message, and the reply, were both posted from this workflow: Hope this helps. Cheers, Steve

Hi @Berto2002, Re: via email, I'm not sure, but I expect something could be done with Power Automate and the Teams connector. The cloud automation that we have will only create new messages in a channel, and not reply to existing messages, but we will certainly be adding a new cloud automation to perform that action. Typical timeframes usually lrun to weeks rather than months, but depend on the teams workload & other priorities. Thanks, Steve

Hi @Berto2002, Thank you for your suggestion. I've added it to our list, we intend to extend the Teams integrations now that their APIs are out of beta, and will include an operation to perform action. Will let you know once we've built these. Cheers, Steve

@Izu, When you say KBs, do you mean the FAQ's that are against the Service that the Problem has been raised against? If that's the case, then no, they are not deleted. Thanks, Steve

Hi @Caroline, The utility now been updated to support these changes in the platform, and can be downloaded from Github. Cheers, Steve

Hi @Caroline, We'll take a look at this issue this afternoon and will let you know how we get on. Cheers, Steve

Hi @aykut.boyraz, The API call in that post will indeed return contact details for a given email address And thanks for commenting @Martyn Houghton, much appreciated Cheers, Steve

Hi @Ann-MarieHolloway, There isn't an alert currently, but I can see the value in having some alerting setup when imports fail. I'll add it to the list and will let you know once we've had chance to investigate possibilities. Thanks Steve

Hello eveyone, We've just released v1.1.0 of the Document Import Utility: Features Added support for setting an owner against imported documents Added caching of created and found tags, so fewer API calls are required into your Hornbill instance Fixed Issue where tags containing backslash characters could not be found This can be downloaded from Github, and is documented on the Hornbill Wiki.

Hello everyone, We've just released v1.2.0 of the Database Asset Relationship Import Utility. This release requires Service Manager build 2241 or above. Changes Updated tool to support move of Configuration Manager into Service Manager Added version check against Github repo Improved logging back to Hornbill instance This can be downloaded from Github, and is documented on the Hornbill Wiki.

Hello everyone, We've released v1.16.0 of the Database Asset Import Utility. This release requires Service Manager build 2241 or above. Features Added support for importing Software Asset Management records when creating or updating assets Improved logging, including: grouping log details per-asset; basic log details added to instance log Added version check against Github repo Changes Optimised import process, including the local caching of Hornbill asset records for each class & type Refactored code to remove duplicated & unnecessary code Rounded time taken output to the nearest second Fixes Removed a number of possible race conditions when using multiple workers This can be downloaded from Github, and is documented on the Hornbill Wiki.

Hi @Martyn Houghton, This has now been released, and requires the Service Manager update that was released last night: It's pretty basic in this release - it only supports deleting Contacts and Organisations whose IDs are provided. Additional filtering options will arrive in due course, but that will require some additional changes to the Core app. Cheers, Steve

@Izu, This has now been released, and requires the Service Manager update that was released last night: Cheers, Steve

Hello everyone, We've just released v.1.16.0 of the Hornbill Cleaner Utility. This release requires Service Manager build 2241 or above. Changes Updates to cater for move of Configuration Manager into Service Manager Features Added support to filter Requests for deletion by Catalog ID Added support to delete Service Availability records, filtered by Service ID(s) Added support to delete Contact records Added support to delete Organization records Added version check against Github repo Enhanced debug logging, now logs request and response payloads when an API call into Hornbill fails This can be downloaded from Github, and is documented on the Hornbill Wiki.

Hi @Martyn Houghton, I'll add this to the list, it would also be useful in the other import tools that use JSON config. In the mean time, you could always use something like https://codebeautify.org/jsonvalidator, or an IDE like Visual Studio Code, to check the validity of the JSON. Cheers,

Hi @Izu, The code is written, and we're waiting on the next Service Manager update before release. This should be in about a weeks time. Cheers, Steve

Hi @Martyn Houghton, I'll add it to the list, will let you know when we get to it. Cheers, Steve

Hi @Izu, That's not currently possible, and would require changes to both the cleaner tool and Service Manager. I'll add it to the list and will let you know when we've had chance to have a look. Thanks, Steve

Hi @BillP, No worries. Although if you're using smGetReqDetails2, you don't actually need the additional call to getRequestRecord, as smGetReqDetails2 provides an activity stream accessToken in the output params, as well as the activity stream ID in the requestDetails output param Cheers, Steve