First time here? Check out the FAQ!

Selkirk Association - VOW Fields

  • retag add tags

Hello - We have a client stating that the value in the VOWAVM field should be "No" for listing #20183530 but we are receiving "Yes" in the field for this listing and ALL other listings in the feed.

Also, we are receiving "Yes" in the below fields for ALL listings being received in the data feed, which seems odd. vowaddress vowcomment vowinclude

RETS Credentials in use: UN: JBond

Currently importing listings with the below Status values: Active Contingent w/Bump Clause Pending Bank Approval

MLSNotify's avatar
asked 2018-10-11 15:27:35 -0500
edit flag offensive 0 remove flag close merge delete


add a comment see more comments

1 Answer


SELKIRK has two fields defined as VOW:
LV_vow_avm - VOW AVM
LM_char5_14 - Display AVM (This one is on the listing input form)
I do not know why they aren't using the standard vow field.
You would need to contact the MLS directly about this.

bwolven's avatar
answered 2018-10-11 17:44:11 -0500
edit flag offensive 0 remove flag delete link


Did this resolve your questions?

bwolven's avatar bwolven (2018-10-16 12:02:54 -0500) edit

Actually, no. I cannot seem to get a direct answer to this question. Can you please tell me what the value is in the LV_vow_avm - VOW AVM field for listing #20183530? Our client is stating it should be "No", however, we are seeing the value "Yes", regardless of the RETS credentials used in the query. Can you please let us know what value the field is populated with for this listing example?

MLSNotify's avatar MLSNotify (2018-10-16 12:53:05 -0500) edit

The MLS added a new field, different from normal Paragon RETS VOW field.
I'm told you should use LM_char5_14 to determine VOW_AVM status.
Just ignore the normal Paragon RETS LV_* fields for this MLS.

bwolven's avatar bwolven (2018-10-16 13:39:39 -0500) edit

By the way, here's what I show for that listing:
<columns> L_ListingID LV_vow_avm LM_char5_14 </columns>
<data> 20183530 Yes NO </data>

bwolven's avatar bwolven (2018-10-16 13:41:37 -0500) edit

Thanks, everyone! Thank you for the thorough explanation, that is the missing piece to the puzzle. I see that we are not currently importing the LM_char5_14 field, which explains our confusion. If I had caught that earlier, this would be a non-issue, so I appreciate your patience in assisting us. Nicely done and thanks! I'll let you know if we have any issues. Thanks!

MLSNotify's avatar MLSNotify (2018-10-16 14:18:24 -0500) edit

Glad to help.

bwolven's avatar bwolven (2018-10-16 14:20:48 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer