Cullman feed metadata does not have lookup field values
We are trying to hookup a new feed to our data intake process. We are able to login and download the metadata, but what it returns in the XML does not contain normal lookup values that we pass to the endpoint. Example...
https://api.(removed).com/v2/Property... eq Enums.StandardStatus'Active') and MlgCanView eq true and OriginatingSystemName eq '(removed)'&$top=5&$count=true&$expand=Media,Rooms
So this is requesting from a "lookup" field the Standard Status= Active. Normally we are given a list of statuses that we can query for in the metadata. Ex: Active, Closed, Pending...etc
Cullman has the fields marked as lookup, but thats all the info given.
<property name="Appliances" type="Collection(Edm.String)" nullable="true"> <annotation term="RESO.OData.Metadata.LookupName" string="Appliances"/> </property>
Login name: smlsaIn_House New RETS Web API: https://smlsa.paragonrels.com/OData/S... Web API Metadata: http://smlsa.paragonrels.com/OData/SM... Access Token URL: https://smlsa.paragonrels.com/OData/S...
You can use something like this to pull the lookups:
In the metadata the lookup name is in the Annotation:
<property name="StandardStatus" type="Edm.String" nullable="true" maxlength="25">
<annotation term="RESO.OData.Metadata.LookupName" string="StandardStatus"/>
Ok, so we are able to get lookup values now. Question, some fields are listed as lookup in the metadata, such as BuyerOfficeAOR in the resource Property, but when queried for it, we get a 200 and empty list returned. Are these lookups that Cullman doesnt use?
Next, we queried for StandardStatus = Active and got our results, but some fields return with a , such as Sewer. Sewer is a lookup field and has lookup values, but when you try any lookup value it returns a 500 error. Ex:
Also, are there any docs to reference? We were only given 3 urls and 1 example queries for login.
Since the type is Collection you would need to use a Lambda expression like this:
<property name="Sewer" type="Collection(Edm.String)" nullable="true">
<annotation term="RESO.OData.Metadata.LookupName" string="Sewer"/>
still having issues querying... figure out how to do more than 1 field such as in the documentation here https://github.com/RESOStandards/tran...
We need to search by more than 1 status and get a 500 trying to build logical and/or. Example
I can do (PropertyType+eq+'Residential')+and+(StandardStatus+eq+'Active'), but no mater how i format multiple StandardStatus I get a 500.
I need to be able to do residential and (active or coming soon or sold etc etc). Can you help with this?
A quick follow up from the other day. I was able to verify the syntax from above works just fine for me using Postman. Though, please be aware the Cullman data feed from SMLSA does not include the Incomplete status. If you'd like to start getting those listings, please reach out to the MLS.