Software Update 03-Dec-2014

Changes

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.

INSTALLATION

There is no requirement for anyone to be back from roaming when you apply this update. If you haven’t already upgraded to version 1.6.0.40, you should follow the procedures for that release before installing this version.

DOWNLOAD

The following file is available for download: mvp-1.6.0.43.zip (~2.4 MB)

INSTALLATION

You should be at version 1.6.0.40 or later before performing this upgrade. To upgrade: Extract the contents of mvp-1.6.0.43.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 1.6.0.43 (Rev. 726). The database version should be unchanged at 1.0.1.87. 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.

Component analysis – verification columns

There are four columns that are generated after the list is initially stocked with components, and if your computer (or the server) isn’t quick enough, you’ll see these fill in line by line. The four columns are Properties, Verification, Total Verified, and Verified (5 Year). If you’ve rearranged your columns, you may not see them in this order.

Properties

The value in this column is simply the number of non-cancelled properties in the component.

Verification

The value in this column is the number of properties that LPI is aware of having been verified. To put it another way, it’s the number of properties that have “VERIFIED” or “INSPECTD” and an associated date in the header record for the property, as shown in this image:

verification-header

There are no date restrictions applied to the values in this column.

Total Verified

The value in this column is the number of properties that MVP sees as having been verified ever. As per the “Verification” column noted above, there are no date restrictions applied to the values in this column.

Verified (5 Year)

This column’s label is a bit of a misnomer. It’s actually the number of properties that have a verification date on or after the cycle start date for the relevant district. When looking for a verification date to compare with the cycle start date, MVP will check the future year, the LT year and the property header record (as described for “Verification” above).

You can see the cycle start date if you go to Tools.Options.Lists.Districts. If there is a cycle start date, it will be displayed in the right-most column. You can edit this date by double-clicking the district entry.

If you want to see the number of properties verified since (for example) the most recent November 1, you can change the cycle start date on the relevant district to that date, and refresh the component analysis window.

MVP User Group Meeting 11-Nov-2014

Date: 26-November-2014
Time: 9.30am Registration to 4.30pm
Location: API Offices, Level 3, 60 York St, Sydney
Cost: $40 per delegate
RSVP: 15-November-2014
  1. 10.00 Welcome
  2. 10.05 Review of changes since last meeting
  3. 10.30 Review of new feature requests
    1. Make the description columns in the improvements, sale adjustments and market movement tabs on the analysis window expand so that the grid takes up all of the available width.
  4. 11.00 QA and associated reports
    1. Report renames
    2. Report accuracy, number of decimal places
    3. Timing of reports, LPI vs MVP
  5. 11.30 MVP’s annual values audit report
  6. 12.00 Changing integrity checks
  7. 12.30 Lunch
  8. 13.30 MVP3 (MVP in the cloud)
    1. Performance & Availability
    2. ValMap integration
    3. System demo
  9. 14.30 Phil’s overview of usage and general Q&A
  10. 15.30 Other items for discussion

Software Update 28-Aug-2014

Changes

Search for verified properties doesn’t work (MVP-225)

The program was attempting to query the database incorrectly when you tried to search for verified properties. It does the right thing now.

Show rate/m² or rate/ha on Benchmark Report (MVP-239)

Pretty self-explanatory, this one. The rate/area values are only showing up on the program at present. The component report printout will be updated if required, and can be released independently of the program itself.

Fix auto population of risk ratings and codes (MVP-248)

The major part of this was released with version 1.6.0.40, but there was an omission. The program now sets the risk rating date to the current date when carrying ratings forward instead of copying last year’s date.

Reference benchmark factors checks (MVP-249)

The Benchmark Factors Checks – Reference Benchmarks (Component Level) section of the annual values audit was using the factor on the property instead of the ratio between the LT and future values. It should have been using the latter, and now it does.

Annual values audit doesn’t take into account multi-property sales (MVP-250)

The annual values audit report was ignoring the “is multi sale” flag on the analysis, and not using the associated land value when doing its checks. It does now.

New export to compare existing risks with defaults (MVP-251)

There is a new export on the Reports page: Risk Rating Comparisons in the Quality Assurance section. This will generate a CSV file that contains a listing of all properties for a district where the actual future risk rating/code differs from the defaults. This can be quite a large listing and may take several minutes to generate, so only use it if you need it.

Include HERITAGE in the default risk ratings (MVP-252)

When determining default risk ratings, the program now checks to see if there is a “14G” valuation basis or a value in the heritage value allowance field. Please see the updated default risk ratings article.

Optionally carry forward risks & valuation bases (MVP-253)

There is now a pair of tick boxes on the Tools.Options.Advanced window that read:

  • Overwrite future with LT valuation bases when factoring
  • Overwrite future with LT risk rating and code when factoring

tools-options-advanced You will find that these are initially ticked because that is the current system behaviour. If you untick these boxes, then MVP will not bring forward the relevant items if there is already something in the future value record. If there is nothing there, the items will be brought forward.

In summary, unticking these means that if you apply a factor to your properties, then change some valuation bases and/or risk ratings away from what the factoring did, subsequent factoring won’t change them. You must untick these boxes for the change to take effect.

Supp import doesn’t take note of risk rating dates (MVP-254)

There were a few problems with the supp imports.

First, it wasn’t taking note of the imported risk dates, and always using the current date as the risk date. It now uses this field (1B-44 in file specification).

Second, the import process was allowing lower risk ratings (higher numbers) to overwrite risks that were already on the value.

Third, and most embarrassingly, the import process was using the LPI risk ratings provided in the file instead of the contractor risk ratings. Back when these were introduced, LPI was providing information in these LPI fields, and at some level, I assumed that they’d keep doing it, possibly using your contractor values where they didn’t have any. But nope. They just stopped, and so the program hasn’t found any risk ratings coming back from LPI. This accounts for the myriad cases where the supps overwrite your risk ratings. This is now fixed.

Finally, the program wasn’t handling the following case: The PE supp was done with valid LG, LT and future ratings (say 2-RURAL on all). However, the sale had already come in and a property entry had been created on the roll. Because the sale had been analysed, the property entry had 1-ANLYSALE. When the completion supp (NE) came back, it created the property officially, and overwrote the 1-ANLYSALE with the 2-RURAL rating. The supp importer now checks for existing property entries when “creating” them, and won’t downgrade the risk ratings if they exist.

If you choose not to proceed with this upgrade, you should ensure that you review the risk ratings on each of the properties updated by incoming supps.

Augment validation rule 254 (MVP-255)

The current Data Load Procedure Manual’s validation rules states that the “B” record validation rule for the annual values file reads

Record was rejected as the risk rating date cannot be earlier than 1st of Nov of the year prior to the base date year

However, they’re sending back this message

Record was rejected as the risk rating date cannot be earlier than the risk rating date of the prior land value, or, where the risk rating has changed, earlier or equal to the risk rating date of the prior land value, or, earlier than the creation date of the property record.

I’ve updated the validation procedure to produce one of several warnings or errors. Here are the messages you can expect to see:

  • (E) The risk rating date must be on or after Nov 1 of the year prior to the base date being exported.
  • (E) There is no LT value to check against the new risk rating date.
  • (W) There is no LT risk rating date to check against the new risk rating date.
  • (E) Record was rejected as the risk rating date cannot be earlier than the risk rating date of the prior land value.
  • (E) Record was rejected as the risk rating date cannot be earlier than or equal to the risk rating date of the prior land value (risk rating has changed).
  • (W) There is no creation date to check against the risk rating date.
  • (E) Record was rejected as the risk rating date cannot be earlier than the property creation date.

I’ve also added warning 245 that tells you that the future valuation basis is different to the LT valuation basis.

Don’t carry the attributable part forward (MVP-256)

Based on the responses received from the question I sent out some time back, you don’t want the attributable part carried forward when you apply factors. The program now no longer does this.

Sale price exception report doesn’t indicate out of line sales (MVP-258)

This report now includes an extra column that lets you know if the sale is out of line. Let me know if you’d prefer them not be included at all.

Allow copy/paste from analyses to component report (MVP-259)

This is a bit of multi-part one. The steps that you take to use this are as follows:

  1. From within the Analysed Sales window (not Sales and Coding), search for the analyses that you’ll eventually want to use to support a benchmark valuation.
  2. Select the analyses that you want to use (Click, Ctrl+Click, Shift+Click, whatever).
  3. Right-click on the window and choose Copy Selected Analysis IDs (or choose the Edit.Copy Selected Analysis IDs). The analysis IDs will now be on the clipboard, so you could paste them elsewhere if you want.
  4. Go to your Benchmark Report window and right-click one of the benchmarks. Choose the Add Analyses from Clipboard menu item. The analyses will be added to the benchmark.

There are a few caveats/notes:

  • The paste operation doesn’t care what sort of IDs you have on the clipboard. If you’ve copied PIDs instead of analysis IDs, it will attempt to interpret them as analysis IDs and most likely fail to add anything to you benchmark.
  • Analysis IDs are not sale IDs. Remembering that you can have multiple analyses per sale, you should be able to see that these can’t have a one-to-one relationship. Don’t go copying sale IDs from anywhere else and expect them to be work in this fashion.
  • If it turns out that you’ve added something that you didn’t really want to add, you can only back out by either removing the sale from the benchmark manually (select the analysis and click the Remove button), or by closing the benchmark report without saving.

INSTALLATION

There is no requirement for anyone to be back from roaming when you apply this update. If you haven’t already upgraded to version 1.6.0.40, you should follow the procedures for the last release before installing this version.

DOWNLOAD

The following file is available for download: mvp-1.6.0.41.zip (~2.2 MB)

INSTALLATION

You should be at version 1.6.0.40 or later before performing this upgrade. To upgrade: Extract the contents of mvp-1.6.0.41.zip into V:\MVP. This will overwrite latest.ver and MVP2.exe, and a report. 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 1.6.0.41 (Rev. 692). The database version should be at 1.0.1.87. 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.