First time here? Check out the FAQ!

Agent and Office Count Discrepancy

  • retag add tags

We have a rets feed with Grand Junction Area RealtorĀ® Association Login url: Username: 17629

For property table like residential, multifamily, land etc we are using queryfiler= (L_StatusCatID=|1,3),(L_IdxInclude=0,2) And For agent table queryfilter= (U_AgentID=0%2b),(U_Status=M)

About half the agents in the property data are missing from the agent data. Can you please look into this?

And also GeoLatitude and GeoLongitude fields are geocode field , can we use that field for geocoding

brokersolutions's avatar
asked 2018-01-17 14:58:54 -0500
edit flag offensive 0 remove flag close merge delete


Are you still having issues with this? If so, are you pulling from Agent or ActiveAgent?

bwolven's avatar bwolven (2018-01-18 10:02:25 -0500) edit
add a comment see more comments

1 Answer


Are you still having issues with this? From what I can tell, some of the agents assigned to listings have U_Status=S and one has U_Status=N. So if you change your Agent resource query to: (U_AgentID=0+),(U_Status=M,S,N) you should get the agents being used.

You could also ask the MLS to enable the LA1_Status, LA2_Status, SA1_Status, SA2_Status fields for your profile so you can see the agent status values in the property data returned. Currently they are restricted for your profile.

As far as the Latitude and Longitude values, you probably need to verify with the MLS whether or not you can use them.

bwolven's avatar
answered 2018-01-18 11:39:58 -0500
edit flag offensive 0 remove flag delete link


add a comment see more comments

Your Answer

Login/Signup to Answer