MetadataEntryID unsupported?
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.
Comments