There was never anything wrong with the data. The only problem was in how it was displayed.
If you are seeing an issue in the data stored in the database, that is some other problem.
Note, that the response data was fixed so that previous data for rates which would have been stored as 0-4, are now stored as 1-5.
And, if you were using named degrees that used values other than the 1-n type (e.g. 2=Easy,4=Not so easy,6=Hard, ...), then the response now show the value of the selection (i.e 2,4 or 6) rather that the position of the degree. But, with the latest releases, the report displays should show the correct choice.
There was also a problem with the restore process, that might have restored incorrect data. That has been fixed in the recent release. If you used a restore operation in using 3.7.0, 3.7.1, and saw this problem, you may have to restore again after upgrading to the latest.
If you are seeing an issue in the data stored in the database, that is some other problem.
Note, that the response data was fixed so that previous data for rates which would have been stored as 0-4, are now stored as 1-5.
And, if you were using named degrees that used values other than the 1-n type (e.g. 2=Easy,4=Not so easy,6=Hard, ...), then the response now show the value of the selection (i.e 2,4 or 6) rather that the position of the degree. But, with the latest releases, the report displays should show the correct choice.
There was also a problem with the restore process, that might have restored incorrect data. That has been fixed in the recent release. If you used a restore operation in using 3.7.0, 3.7.1, and saw this problem, you may have to restore again after upgrading to the latest.