Support

Expand all | Collapse all

Upgrade to 8.31 has broken all our velocity reports

  • 1.  Upgrade to 8.31 has broken all our velocity reports

    Posted 03-01-2019 03:39
    We have upgraded to 8.31 from 8.10 and find that all our Excel Velocity reports have stopped working.  The symptoms are identical to a previous thread; addition of a MIME header with the phrase "3D" sprinkled through the output.  Please see previous post for the description

    Velocity Excel exports not working after switching to Jama 8

    We have tried multiple report templates, stripping reports down to nothing, using the excel base content in the "jama custom report user guide 8.24", creating new reports and ensuring velocity & excel is selected in the report settings.  All reports are showing the same symptoms.  What's changed?

    I'd be grateful for any help with this.





    ------------------------------
    Scott Rocca
    Collins Aerospace
    Malvern
    ------------------------------


  • 2.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 03-01-2019 08:01
    Scott:

    Would you be so kind as to tell me which reports are affected? And did these reports ever work in 8.31?

    Thank you,

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 3.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 03-01-2019 08:15
    Chloe

    All the velocity reports that are configured as outputting to Excel.  All of them are in-house developed.  They worked quite happily in 8.10 but do not work in 8.31.

    Thanks

    Scott


    ------------------------------
    Scott Rocca
    Collins Aerospace
    Malvern
    ------------------------------



  • 4.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 03-01-2019 08:21
    All the reports are configured as 'Microsoft Office XML formats', as per the content in Wikipedia (https://en.wikipedia.org/wiki/Microsoft_Office_XML_formats).

    ------------------------------
    Scott Rocca
    Collins Aerospace
    Malvern
    ------------------------------



  • 5.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 03-01-2019 08:28
    Scott:

    Are you using Excel for Macs?

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 6.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 03-01-2019 08:43
    Scott:

    One of your counterparts has also opened up a Support ticket on this same issue. I will link this Community post into that ticket so that our Support has this information. We have already CC'd you on the Support ticket.

    FYI, I asked about Excel for Macs because, there was some code which was recently added to Excel for Mac which really broke the reports. If you do have an Excel for Macs environment, we would recommend either:

    1.) Running them on a PC or
    2.) on the Mac - run them as Word and then copy them to Excel.

    Looking forward to hearing back.

    Best,

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 7.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 03-01-2019 09:09
    Chloe

    I'm confused; what do Mac's have to do with it.  We're running windows 10 and standard office (2013).

    The problem appears to be that JAMA 8.31 is generating an html report file even though configured that it should be an Excel xml one.  So when Excel opens the (.xls) file it can't correctly interpret the contents (which are a mix of html and Office XML).  This would seem to have its roots in JAMA.

    We're wondering if there is a bug, there is some error in the JAMA configuration or there is something in the vm report file that is causing a reoccurrence of the earlier problem seen with images in reports (linked above)?

    I've received the notice about the support case.

    Thank you




    ------------------------------
    Scott Rocca
    Collins Aerospace
    Malvern
    ------------------------------



  • 8.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 03-01-2019 09:15
    Thank you Scott, we are wondering the same thing. Asked about Excel for Mac's because of some known problems with it, and I wanted to eliminate that as a possibility.

    Thank you for this new information, it will be very helpful for troubleshooting in the ticket.

    Best,

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 9.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 03-04-2019 00:40
    Export the Excel as HTML, then rename the file to xls.

    We have the same issue, this should be SOS-DEF-2401.

    Google does not find "SOS-DEF-2401" so I assume this is not fixed yet.


    ------------------------------
    Harald Hotz-Behofsits
    Frequentis AG
    ------------------------------



  • 10.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 24 days ago
    Hi,
    it seems as if the issue has silently been fixed in 8.49. Can you confirm this, @Chloe? There is nothing in the release notes under resolved issues though.
    Thank you,
    Anna


    ------------------------------
    Anna Henke
    MeVis BreastCare GmbH & Co. KG
    ------------------------------



  • 11.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 23 days ago
    Anna:

    Thank you for communicating this. I checked the defect and it is still open, so your observation about it not being in the Release notes is correct, this is still an open defect. Anna, I have put in an inquiry in the defect. Just for discovery purposes, was there anything you changed in your instance besides upgrading to the new 8.49 version? I am monitoring the defect for a response on this new information and will update this thread when I hear. Feel free to at mention me again if there is a long delay.

    Best,

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 12.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 23 days ago
    Hi @Chloe,
    thanks for checking. We are not aware of any changes we made. So I am curious what you finde out or if @Harald or Scott can confirm this.
    Regards
    Anna
    ​​​

    ------------------------------
    Anna Henke
    MeVis BreastCare GmbH & Co. KG
    ------------------------------



  • 13.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 22 days ago
    @Scott



    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 14.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 9 days ago
    @Chloe, any updates here?
    We would like to finalize our documentation and remove the workaround, in case you can confirm that the issue is fixed.

    Thank you,
    Anna​

    ------------------------------
    Anna Henke
    MeVis BreastCare GmbH & Co. KG
    ------------------------------



  • 15.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 8 days ago
    Anna:

    Thank you for checking in, at this point we are thinking it must have been an upgrade on the MS side of things. Perhaps in combination with some upgrades we have done, but cannot pinpoint a direct cause for this yet. I would be interested to hear if this is something the other community members in this thread are experiencing as well.

    I apologize for not having a more direct answer, I would perhaps change the documentation but, keep a caveat that this fix was unknown and if it does show up again; here is the workaround?

    Best,

    ------------------------------
    Chloe Elliott
    Jama Software
    Portland OR
    ------------------------------



  • 16.  RE: Upgrade to 8.31 has broken all our velocity reports

    Posted 3 days ago
    @Chloe,

    our workaround was to remove all images from the reports by using a regular expression: ​$vDoc.document.description.replaceAll("<(\s*)img[^<>]*>","")
    I got an automated email today that said that SOS-DEF-2104 was not present anymore in Jama which relates to this problem. Maybe there is a mixup of the numbers assiciated with this anomaly?

    Anna

    ------------------------------
    Anna Henke
    MeVis BreastCare GmbH & Co. KG
    ------------------------------