Critical issue in the production release

[brucet]

Unfortunately a critical issue has been reported in the initial v18 production release, which can cause reports to fail in sites upgraded from Sellerdeck 2016 only. Upgrades from Sellerdeck 2014 and earlier are unaffected.

We are working on a fix and will issue a new build as soon as possible.

To fix the issue in any sites you have already upgraded, please do the following:
1. Download this zip file, which contains the v18 reports: http://downloads.sellerdeck.co.uk/v18-Reports.zip
2. Extract the files and copy them to your site folder, overwriting the files already there. If you have more than one site, you must copy them to the site folder for each one.

We apologise for any inconvenience caused.

[harlex]

Does this only affect upgraded sites or does it also affect sites imported with a snapshot?

[brucet]

It affects snapshot import and File | Import Sites. I don't know if we've explicitly tested upgrade on installation, but I would expect that to be affected as well.

[zgap111]

I'm amazed this wasn't picked up on the beta tests...

I normally just use our custom ones and every major update (eg. v14 to v16) change the database link ("Set Location" I think, and figure out what other variable name changes...)

...and when it doesn't work, then it's 5+ hours of customising the default new rpt files to look like our current ones... a pain.

If there is a problem, I assume some changes have been made to the reports...

Is there a list of changes you've made in the reports?

A list would be nice, as I'd rather spend minutes to update some variables than spend hours on re-doing customisations on whole reports...

[brucet]

There are no specific changes to the reports. However, with each major release, all the reports have to be modified so that they point to the site databases from the new version.

Due to a fix for another upgrader issue that was applied very late in the development process, this upgrade is not applied in the production release.

That's in a nutshell and as I understand it at this point in time.

We are testing a fix and hope to have a new build available tomorrow.

[Jan]

Tak - you can just change your custom reports to point to the new database but you are essentially throwing away any changes that have been made by Sellerdeck as part of the release. It is usually sufficient to check the release notes to see if there is anything significant and if not, just change the location. Sometimes changes made are internal - as an example, when the program changed to allow tax inclusive and tax exclusive product values the reports were reworked to cater for this. Having said all of that , the reports don't appear to have changed significantly over the last few releases. I sometimes export the new and old reports to XML and then compare the text files produced to check changes as well.

Kind regards,

[zgap111]

Thanks Bruce and Jan

It is usually sufficient to check the release notes to see if there is anything significant and if not, just change the location.

I haven't found any release that mentions changes to the reports
- I think many years back there was a change in the credit card number variables...

Exporting to XML is interesting...
- just tried it, could not find "export" in the menu's but found it as a button on the toolbar(!?), exporting takes a little time and the file is huge

I seem to learn a little more Crystal reports (every two years...)