Active Reports 13 JSViewer with Active Reports Server 12

Active Reports 13 JSViewer with Active Reports Server 12

Posted by: dave.willis on 6 February 2019, 1:13 pm EST

• 

  dave.willis

  • Post Options:
  • Link
    Copy

  Posted 6 February 2019, 1:13 pm EST

  I’m trying to use the new JSViewer bundled with Active Reports 13 on our Active Reports Server 12 installation, and I am encountering the following CORS issue caused by the active reports server running on a different origin to the client site:

  
  Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at http://10.0.0.152:8080/reports/RecordHours/info. (Reason: missing token 'cache-control' in CORS header 'Access-Control-Allow-Headers' from CORS preflight channel).
  

  Is the new JSViewer compatible with ActiveReports Server 12? If so, would someone be able to provide direction to help me solve this issue?

• 

  dave.willis

  • Post Options:
  • Link
    Copy

  Posted 7 February 2019, 5:34 am EST - Updated 30 September 2022, 3:49 pm EST

  I managed to get around the above CORS issue by adding the following headers to the server’s web.config:

  Cache-Control, Expires, Pragma

  However I am now encountering an issue with retrieving the report:

  

  This works fine with the HTML5 viewer but we would like to utilise some of the new features of the JSViewer ASAP. Could anyone give direction as to whether the JSViewer works with an ActiveReports 12 server? And if so what am I doing wrong? For further context the report is an RDLX based report (I’ve tried providing the .rdlx extension on the report type param), and it belongs to the ‘Root’ location with a custom category.

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 7 February 2019, 5:46 am EST

  Hell Dave,

  I have escalated your question to our development team(269852) and will inform you once I get any information from them.

  Thanks.

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 7 February 2019, 5:46 am EST

  Hell Dave,

  I have escalated your question to our development team(269852) and will inform you once I get any information from them.

  Thanks.

• 

  mohitg

  

  • Post Options:
  • Link
    Copy

  Posted 8 February 2019, 2:42 am EST

  Hello,

  As per reply from the developer, It is not possible to use AR13 JS viewer with the AR12S.

  Thanks.

• 

  dave.willis

  • Post Options:
  • Link
    Copy

  Posted 11 February 2019, 5:08 am EST

  Hi Mohitg,

  Is this a permanent decision or is there plans to support it in the future? If so is there a timeline for this support? The JSViewer seems a much better match for the functionality we require from ActiveReports and I’ll be honest that I am very disppointed with the performance of the HTML5 viewer.

  Thanks

• 

  annupurnap

  

  • Post Options:
  • Link
    Copy

  Posted 13 February 2019, 4:43 am EST

  Hi Dave,
  
  We are sorry but there are no plans to support it in future.
  
  Regards,

• 

  dave.willis

  • Post Options:
  • Link
    Copy

  Posted 13 February 2019, 1:09 pm EST

  Hi Annupurnap,

  That is extremely disappointing, considering we are paying a not insubstantial amount of money for your server product we expected at least parity with your less expensive option. Is this a sign that your server product is reaching end of life? If so I think you should alert your customers to this so they can look at alternative solutions. This decision will definitely make me think twice about renewing the product, and recommending and using your products in future.

• 

  annupurnap

  

  • Post Options:
  • Link
    Copy

  Posted 14 February 2019, 1:52 am EST

  Hi Dave,
  
  Sorry for the miscommunication.
  
  I meant there are no plans to release any more features in AR12-JSViewer. It does not mean that server product will stop. It will continue with AR13 version.
  
  Also JSViewer got a lot of specific changes in v13 hence it won’t be compatible with AR12 version.
  
  I understand that you wanted to use AR13-JSViewer with AR12 but I am sorry it is not possible.
  
  Would suggest to use it with AR13 only.
  
  Hope I am able to explain it now and sorry again for the confusion.
  
  Regards,