[Reporting issues - csv output corrupted]

1 hour ago, Steve G said:

I've just released version 1.6.0 of the Hornbill Data Export Tool, which supports the use of the XLSX files from reports, as well as the existing CSV file support. It can be downloaded from Github, and is documented on the Hornbill Wiki. Specifically, look for UseXLSX in the Configuration section, and make sure you switch XLSX on in the report config > Output Formats > Additional Data Formats:

 

Thanks, Steve! Will look at implementing that. 

[Reporting issues - csv output corrupted]

We are having a problem with our CSV exports too, but this is with the goHornbillDataExport tool, so I don't think the xls workaround will work for us. Do any of the developers have an estimated time this might take to fix? Would be good to know if we need to look into alternatives or wait it out. 

[Knowledge Centre]

Would be really interested to know when this functionality is available too!

[Xmlmc method invocation failed for BPM invocation node]

Hi @Lauren how did you determine it was a fault in your local network?

[Xmlmc method invocation failed for BPM invocation node]

@Lauren

Every time we have had this, when we restart the failed bp it continues as normal, and we still haven't made any changes to the BP or email template since well before this started happening.

 

Edit - Haven't actually had a problem restarted bp, it was just a few tickets in a row that errored at the same point.

[Xmlmc method invocation failed for BPM invocation node]

Just want to update the ticket to say this is still happening for us, would appreciate any suggestions or updates!

 

Quite an inconvenience when there are no hornbill admins around to repeat the failed stage.

[Custom fields not pulling through to email]

Thanks @Steven Boardman will give that a go, hopefully resolve it! 

[Custom fields not pulling through to email]

Sorry! Images attached.

[Custom fields not pulling through to email]

Hello,

We have had this issue twice now on our log against existing standard change tickets, with it all working correctly in between the incidents and no changes made.

This is what it looks like when it doesn't work:

This is the section of the BPM that is grabbing the scheduled date and time and assigning it to custom field 22/23.

Below is part of the config showing the custom fields being updated with the start and end date.

 

Below screenshot is showing the get request details before the email is sent out.

Part of the get request details node config.

 

We cannot see any issues within the BPM of email template as this has worked for the majority of standard changes sent out apart from a couple that have emailed out just showing the custom field tag rather than the data it should be pulling. 

Could someone please take a look for us?