CRYSTAL REPORTS

REALLY want to know why SAGE 50 Canadian did not tell us that they were going to discontinue the capability to use Crystal Reports for forms. 

The fact that we hear about this part way through the year is ridiculous. Add to that the fact that they have not improved the functionality of their own report designer and they cannot open up the channels for us to choose more data fields thus replacing our Crystal Reports formatted form within their own software. 

They offer no solution to the problem they simply state that as of June 2014 CR will cease to work.

Very amateurish on their part!!

Parents Reply Children
  • in reply to MITAITHECAT

    The Sage approach is to allow an export of the data that the old Crystal Reports forms used to use.  

    When printing the Sage forms, the data export doesn't happen, andinvoice has not been posted  It's not yet possible to query the database for other information relating to the invoice, so the only data available is what is being sent to the print driver.  (even though the Project data is available, it's not possible to know which Projects are allocated to the invoice.

    There are already some third party products that use other triggers to work around the lack of any print integration.  (i.e. they watch for a data file to be created, or watch the Sage 50 database for any updates to the tables that store invoices (XLGL appears to do this).

  • in reply to RandyW

    I have a working solution for this. You setup a NUL print driver and use that as the default for the forms, then I have a C# program that monitors for changes to the CSV files and auto-prints the Crystal Reports. I'm able to custom-select the report based on the customer type, print any type of form, etc. It works quite well.

  • in reply to Justin Cowling

    I had thought that the Crystal Reports CSV files did not get updated when the Sage 50 type forms were selected - that's how it acted up to the 2014.2 release.  

    For the 'Sage 50' forms, there were a half dozen printing fields added for 2015 as a sop for pulling the Crystal Reports integration in the 2014.3 release, but then there was a new bug introduced in printing January 1, 1901 in blank ship date fields.  This was fixed in the 2015.2 release, and now there is a bug in the form selection.  Thanks for trying, Sage.

    Kudos to all the independent developers working to keep a reasonable level of form printing capability available.

  • in reply to RandyW

    There is an option in the form setup to continue generating the CSV files.

  • in reply to RandyW

    Randy,

    Justin is correct.  The option to export csv files is at the bottom of the Setup, Reports & Forms left-hand part of the screen (Form Data Export I think, going from memory).  It's been there since the release of 2014.3 but there is/was a significant bug in it, in that it will turn itself off "somehow" on network systems.

    I do not know if that bug has been fixed.  Sage has not told me they found it and fixed it, it doesn't look like it was addressed in the 2015.2 release notes, and my clients have not told me it is still a problem. (though they all know about it and how to workaround it, and my program gives the user the option to set it for them if it is not set, but they have to reopen Sage 50 for their instance to see it).

    The setting mentioned above is not a user-defined setting (as are all other Reports & Forms settings), it is a company-wide setting.  Set it once by any user capable of setting it and it is supposed to be set for all users but all users must then open the file after that to see the flag has been set.  If they have the file open when another user sets it, that instance of the program will not know it is set because it is only read at the opening of the file.