Sale price exception report doesn’t indicate out of line sales (MVP-258)
There is a new column in the sale price exception report that indicates whether or not a sale noted in the report is also noted as out of line.
Mislabeled reports (MVP-261)
A couple of the reports had dodgy icon labels and titles. These have been brought into line with LPI titles.
|MVP icon label||MVP report title||New label/title|
|Variation by Factor||Factor by Variation||Land Value Ratios Check|
|Variation by Sale||Sale by Variation||Land Value Greater than Purchase Price|
Land values ratio in annual values audit wrong (MVP-262)
The calculation for this item was just flat-out wrong. It was involving sales where there was no need to. It now does the right thing, finding properties where factors are less than 0.5 or greater than 2.0.
Bad info messages in market data export (MVP-264)
The info messages saying that the benchmark property has no associated sales wasn’t showing relevant information in the last column. Rather, it’s just including the last line from the file. This has been fixed, along with the message that lets you know that there is no primary benchmark associated with a component.
Add new validation checks for market data (MVP-265)
There were 4 new validation checks specified by LPI:
- 259: Record was rejected as the adjusted land value must be null for a non market sale
- 260: Record was rejected as the adjusted land value is $0
- 261: There are no sales with market indicator Y and out of line indicator N
- 262: The number of sales with market indicator Y and out of line indicator N (x) is less than the number of sales with market indicator Y and out of line indicator Y (y)
These have been included in MVP integrity checks.
Internal analyses showing up in reports (MVP-266)
The following reports had internal analyses impacting statistics:
- Sales activity
- Statistical chart
- Statistical measures detail
- Annual values audit
- Comparison of average value changes
This is no longer the case.
MVP crashes when too many properties sent in from ValMap (MVP-267)
If there are too many PIDs sent from ValMap to MVP (such that the number of characters in the command line string > 64), the program could crash.
Although people said at the MVPUG meeting that it wasn’t a problem, I’m at a loss as to how it couldn’t be. Anyway, it’s fixed now.
Ensure that importing the roll from LPI doesn’t overwrite LG risk ratings (MVP-269)
The problem here is that LPI only provides a single set of risk rating information for any given property. The import process was applying that information to both the LT and GVal years when it should only have been applying it to the LT year. Only the LT year’s information is updated now.
If you’ve imported an updated roll from LPI AND it’s mucked up your GVal risk ratings AND you have a database backup from just before you imported the roll, please let me know. I can use the backup to restore your GVal risk ratings.
Add new integrity check (E260) for market data file (MVP-270)
Actually, there were several new integrity checks added as a result of this issue:
- Market data
- B247 – Component factor is not between 0.001 and 9.999.
- C256 – The change between previous LV and LV is outside the authorised factor range. Actually, this will never fail. The check is there as a placeholder because I can’t determine what the authorised factor range is. Please let me know if you know.
- E233 – District code 999 in analysed sale record does not match that in the header record.
- E257 – The out of line sale indicator cannot be null and must have a value of Y or N or the out of line sale indicator field is missing from record.
- Annual values
- B250 – The risk rating information is incomplete (if any risk information is present, all risk information should be present).
If you’ve noticed that the title of the request includes E260, and that E260 wasn’t noted in what was actually done, it’s because it was covered in MVP-265 above. Ahem.
Reinstate zoom into sale summary (MVP-274)
I’ve put the zoom button back on the sale analysis editing window for the sale summary. You can click that button to and a new larger window will open up with the sale summary inside. You can edit it there, and have it put back into the regular location.
I’ve also made the font size somewhat larger in that window so you should be able to see the text more easily.
Resize calculation grid (MVP-275)
Resize the grid in the calculations tab, and get the description to expand so it takes up the slack space. This applies to both worksheets and to sale analyses.
Show total calculated value on worksheet window (MVP-276)
The request was to show the total calculated value somewhere on the window, and two options suggested were under the existing value field on the main window; and as a new row on the calculation table.
Due to the twin advantages of being easy for me to do, and the permanent visibility of the number for when you switch to a different tab, the total has been put on the main window instead of the table.
Extra column in District Detail report (MVP-278)
There is an extra column in the district detail report containing totals for the GVal year. The GVal year in the column heading, so make sure you check that if the GVal and LT year columns look the same. If the GVal year is the LT year, this explains why.
Field lengths in exports (MVP-279)
The program now ensures that the various comment fields are limited to 4000 characters, purchaser and vendor names are limited to 50 characters, and the valuer name is limited to 20 characters in the market data export file.
Changing components for PIDs (MVP-280)
When a PID moves component, the program now asks if the corresponding sales should move as well.
Note that this is when you move the PID from one component to another from the Property Edit window. It doesn’t do anything with supps.
Show analysis date in search results (MVP-283)
The request was to have the most recent analysis date shown with the valuation roll search results instead of just a “Yes”. The problem is that the “Yes” indicated the presence of a sale, not of an analysis. If I changed it to be the date, you would lose the ability to see sales that had no analyses.
Remove the QRP from the Sales Activity Report (MVP-284)
The QRP column has been removed from the sales activity report, as has the notification that the report relies on data from the component data table.
Note that this is not the change that results in quartile information being included for analysed sales. Looking at the report, it’s going to be easier to just write a new report.
To answer this need, I’ve added a new column: Last An. This column will contain the most recent analysis date for a property if one exists. You’ll find the column on the far right-hand end of the table.
There is no requirement for anyone to be back from roaming when you apply this update. If you haven’t already upgraded to version 126.96.36.199, you should follow the procedures for that release before installing this version.
The following file is available for download: mvp-188.8.131.52.zip (~2.4 MB)
You should be at version 184.108.40.206 or later before performing this upgrade. To upgrade: Extract the contents of mvp-220.127.116.11.zip into V:\MVP. This will overwrite latest.ver and MVP2.exe, and several reports. Start MVP2 on your computer and step through the regular upgrade process. Once you have been able to upgrade the program, choose Help.About MVP… to confirm that you are running version 18.104.22.168 (Rev. 726). The database version should be unchanged at 22.214.171.124. If you have any trouble downloading or installing, make sure you have read this entire article, and then, if you’re still having trouble, please call Phil on 0414 718 297.