Jump to content

chriscorcoran

Hornbill Users
  • Content Count

    361
  • Joined

  • Last visited

  • Days Won

    2

chriscorcoran last won the day on May 7 2017

chriscorcoran had the most liked content!

Community Reputation

17 Good

About chriscorcoran

  • Rank
    Senior Member

Profile Information

  • Gender
    Male

Recent Profile Visitors

1,468 profile views
  1. Are there any issues with email being sent from hornbill this morning?
  2. Seems a lot better now! Thanks if anything was done
  3. Happy New Year, Hornbill team! I'm finding Hornbill really slow this morning, failing to load requests lists and email inbox, not sure if anyone else is seeing this? All other internet sites seem to be reposning fine.
  4. I have created a couple of extra fields in the request details section. I need to report on those fields. How do I find out what they are called in the reporting console? I assume they will be called CustomA etc?
  5. @Steve Giller not sure if its officlally been fixed but I have switched back to csv using the latest R script and my dashboards are now updating OK. Thanks.
  6. script attached, im using minus instance and key hornbill script.txt
  7. Hi @Steve G I have given it a try today but getting error below. I noticed the report seems to be still trying to output as csv even though I selected xlsx, thanks
  8. I have gone back to the report it is using in Hornbill and when I export the csv the report is corrupt. Looks fine in preview. Are there issues with the reporting?
  9. spoke to soon getting the following when I updated the script in my source settings OLE DB or ODBC error: Type mismatch. (Exception from HRESULT: 0x80020005 (DISP_E_TYPEMISMATCH)).
  10. My bad, typical man, hadnt read through readme, I forgot the issue of Details: "Unable to translate bytes [E2][80] at index 0 from specified code page to Unicode. is caused by UTF-8, chnaged it to ISO-8859-1 This will usually be "UTF-8", but if you have issues returning data with certain characters (the Windows E2 80* characters are the usual culprits) then choose a different character set to use, ie: "ISO-8859-1"
  11. I did notice a new script posted in git so I have tried thet but now get We encountered an error while trying to connect. Details: "Unable to translate bytes [E2][80] at index 0 from specified code page to Unicode." Tested on two seperate reports that use R and both fail with the same error.
  12. Just refreshing a report this morning and getting the following erro, nothing I know of has changed. I have set myself a new API key just in case but I still get ADO.NET: R script error. Error: Argument 'txt' must be a JSON string, URL or file. Execution halted Any ideas?
×
×
  • Create New...