Ask Your Question

Revision history [back]

Sorry for the confusion with the NEREN field changes.

The field addition list wasn't as exhaustive as it could have been.

There are several ways you can handle the field changes:

  • Use Select parameter when searching to specify the fields you are using, then it wouldn't return any new fields. There could be issues if columns are removed.

  • Return all the fields but check the column header and use only the ones you are concerned about.

  • Check the column header against the columns you expect and update your data accordingly.

It is always best practice to check the column header returned by search to verify the data is what you expect. Some RETS implementations may remove columns that are advertised in the metadata based on business rules which is perfectly valid in RETS. Paragon RETS leaves the column but blanks the data based on business rules.

As far as the LO* and SO, these were originally added to the listing data to make it more convenient for RETS clients so they didn't have to pull office data separately to get some of the basic office information. Since these fields were added to Office, they show up in the corresponding listing fields too. This would apply also in the case where fields are added to the Agent resource, they would show up in the LA and SA* fields.

The other fields were ones that were enabled in Paragon at some point, but weren’t in RETS yet because a RETS refresh hadn’t been done yet.