First time here? Check out the FAQ!
0

MAXEBRDI Agent/Office not cross mapped to "MLSListing" property records

  • retag add tags

Login URL: maxebrdi.rets.paragonrels.com/rets/FNISRETS.aspx/MAXEBRDI/login?rets-version=rets/1.5

User : '206534181'

Running into a problem with a large number of property records attributing the Listing Agent and Listing Office to "MLS ListingsX", which looks like are associated with the MLSLisings data share MAXEBRDI has. The code in the "L_ListAgent1" field does not correspond to any codes in the Agent or ActiveAgent resource so I can't look the names up. The code in the L_ListOffice1 field all correspond to "MLSListingX in the Office resource.

Example listing: L_DisplayId=ML81710275

We know the Listing Agent is Lily Pizano because her office is our customer and is making the complaint, and she does have a record in the ActiveAgent Resource: Agent Identifier 147283 but that appears nowhere on her listings.

Is there anything we can do about this or is this an MAXEBRDI issue? Non MLSListing listings are not affected. Those all map just fine.

-Len Vinci iHOUSEWeb, Inc.

LenVinci's avatar
LenVinci
asked 2018-06-18 11:16:03 -0500
edit flag offensive 0 remove flag close merge delete

Comments

add a comment see more comments

1 Answer

0

I checked and the data is the same in MAXEBRDI Paragon too. You will need to contact the MLS and work through them to get this fixed since it isn't really a RETS issue.

bwolven's avatar
bwolven
answered 2018-06-18 15:40:09 -0500
edit flag offensive 0 remove flag delete link

Comments

That's what I was afraid of. Thanks though!

LenVinci's avatar LenVinci (2018-06-18 17:48:13 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer