Ask Your Question

Revision history [back]

I notified the SSM who will coordinate getting this fixed.

I notified the SSM who will coordinate getting this fixed.

Update 2016-11-23 15:20 CST: Still waiting for the refresh to be approved and scheduled.

In the mean time you could break it up into two requests. One that excludes that lookup value to get everything but those. And a second one that Only includes that lookup value. Even though it fails, you would still get the data. It just includes the undecoded value for the field since it isn't in the lookup metadata.

You can also do the search using COMPACT which will return the undecoded value for the field and use the lookup metadata in your client to populate the decoded value. Then you have much more control over how they are handled and the download won't return an error.

I notified the SSM who will coordinate getting this fixed.

Update 2016-11-23 15:20 CST: Still waiting for the refresh to be approved and scheduled.

In the mean time you could break it up into two requests. One that excludes that lookup value to get everything but those. And a second one that Only includes that lookup value. Even though it fails, you would still get the data. It just includes the undecoded value for the field since it isn't in the lookup metadata.

You can also do the search using COMPACT which will return the undecoded value for the field and use the lookup metadata in your client to populate the decoded value. Then you have much more control over how they are handled and the download won't return an error.

Update 2016-12-07 14:25 CST: Sent followup request about RETS Refresh.

I notified the SSM who will coordinate getting this fixed.

Update 2016-11-23 15:20 CST: Still waiting for the refresh to be approved and scheduled.

In the mean time you could break it up into two requests. One that excludes that lookup value to get everything but those. And a second one that Only includes that lookup value. Even though it fails, you would still get the data. It just includes the undecoded value for the field since it isn't in the lookup metadata.

You can also do the search using COMPACT which will return the undecoded value for the field and use the lookup metadata in your client to populate the decoded value. Then you have much more control over how they are handled and the download won't return an error.

Update 2016-12-07 14:25 CST: Sent followup request about RETS Refresh.

Update 2016-12-08 11:52 CST: The RETS Refresh has been completed. Please verify that your issues are fixed and add a comment this site. Thanks for your patience.