City Mapping

I am wondering if PIRETS is getting the possible keys for residential, then ignoring the other classes, which appear to have different keys entirely. Do I need to ask FlexMLS to format them differently? Is there something I can do? The values look right in the field options settings, it's just a problem that it displays the cryptic keys, instead of the values, on the nodes that aren't residential class, and displaying the key instead of the value in the Location field mapping. I seem to remember this not being a problem in earlier versions, but I may be wrong.

Just to make sure I'm being clear, when I query on LIST_1 (listing ID field that is mapped to PIRETS CCK's MLS Identifier field), LIST_39 (city) returns a cryptic string ("JDA8FR5MZOY" or something similar), but when I query on LIST_15 (status) instead, it returns a string with the actual name of the city ("Tillamook"). My problem is that the cryptic string is what is displaying the node.

Ok, good news, I was able to fix it by adding "?Format=COMPACT-DECODED&SearchType=Property&" to the default for URL for searching. The only problem now is that there is an extra "?" in my query string, but it seems to be working fine regardless. I think with a couple tweaks, PIRETS could support FlexMLS without a hitch. Perhaps add a less hacky way to add parameters to the query string?

This issue actually affects all PIRETS multi-select fields where the MLS returns a code, rather than a value, for its list of possible values. PIRETS seems to initially query all possible values during setup for the A class (residential class), but it does not get the values for other classes. The result, with my MLS, is that the fields populate with the code, but not the corresponding value. The results can be quite problematic, as I have noted in this other issue I created. Is there a workaround? What DMQL query can I use to determine the possible values and corresponding codes for each class? I will likely be modifying the CCK field allowed values, unless there's a better way.

Using most recent from drush. (drush dl pirets-6.x-3.x just yesterday). Posting file attachments just to be clear. The city in the location field should appear the same as the value of the City field, but it's picking up the MLS's code instead of the value.

For the record, the first sites that used PIRETS used the same values for lookup fields regardless of the property class.

Yes, I see that in this old issue, which I have apparently duplicated in this new issue, which is identical, yet still seems to be occurring in the most recent dev release. Feel free to close it and open the old one, or whatever.