First time here? Check out the FAQ!

MetadataEntryID unsupported?

  • retag add tags

I've noticed that Paragon seems to generate random alphanumeric strings for MetadataEntryID on LookupValues in RETS. According to the RETS specification:

This field, a 32-character string, is to be maintained by the server and can be used by the client to indicate that a particular row has the same logical meaning despite changes in its fields. For example, the invariant field may be used to detect changes in the SystemName in the Table metadata.

We use this field to track changes to lookup values, but it seems as though the Paragon system does not implement it faithfully. It works in every other major MLS system.

Here is an example from MiRealSource metadata version 17.4.15856, Date 2017-04-11T00:16:17.3Z

{ "MetadataEntryID": "0DE4443299B65A380871", "LongValue": "West Sumpter", "ShortValue": "WestSumpte", "Value": "WestSumpte" }

Now, in the current version: 20.3.13922, Date 2020-03-09T16:02:29.6Z:

{ "MetadataEntryID": "0DE4443299B65A380871", "LongValue": "Walhalla", "ShortValue": "Walhalla", "Value": "Walhalla" }

If you check the previous metadata version, 20.2.27655, the value is not present at all.

Can you comment on why the platform behaves this way? In my opinion, not producing the value at all would be better than producing an ever-shifting one.

mtb8332's avatar
asked 2020-03-27 13:39:40 -0500
edit flag offensive 0 remove flag close merge delete


add a comment see more comments

1 Answer


I've actually never had this one come up as an issue before. But you are correct.
The METADATA-LOOKUP_TYPES, MetadataEntryID value is probably not functioning as desired.
I would suggest, at least for now, just ignoring it in that LOOKUP_TYPES.
The ones in the other metadata values should be working properly though.

bwolven's avatar
answered 2020-03-30 13:54:52 -0500
edit flag offensive 0 remove flag delete link


Ok. We make heavy use of it to track changes to long values over the lifespan of our accounts in a market. Are you able to do something deterministic, like MD5 the unchanging value? People probably aren't relying on it already, so it shouldn't hurt to get one last new MD5ed value and use it going forward.

mtb8332's avatar mtb8332 (2020-03-30 18:23:04 -0500) edit
add a comment see more comments

Your Answer

Login/Signup to Answer