InnoVia to Paragon Conversion: Queries Fail To Produce Field Data

asked 2016-08-13 10:44:10 -0500

This post is a wiki. Anyone with karma >75 is welcome to improve it.

Our NEREN client is currently using the PHP/CentOS based PHRETS library v 1.0.1 and is part of the data feed conversion process from InnoVia to Paragon. This conversion project is absent a client conversion document. Then presumably, all that would be necessary, as we have done for our client, is to change the logon credentials. However, when a valid query, or string of queries are run, the process appears to poll the database correctly, but is absent of any specific results. For example a specific search for current_type [ResidentialProperty] with a SEARCH_QUERY [ListingID=4388051], which residential MLS# has been on InnoVia for months, yields no field data. Is there a client based conversion document available to support the conversion process from InnoVia to Paragon that will remedy this problem?

For example, this simple query in InnoVia works: http://nne.rets.mlxinnovia.com/nne/Se...

This same query formatted for Paragon FAILS: http://neren.rets.paragonrels.com/ret...

Paragon reports the following error: <rets-status replycode="20206" replytext="Invalid Query Syntax. Missing or Empty [Query] Argument."/>

edit retag flag offensive close merge delete

add a comment

2 Answers

Sort by » oldest newest most voted

answered 2016-08-16 09:37:55 -0500

This post is a wiki. Anyone with karma >75 is welcome to improve it.

The logon provided on Friday, 8/12/2016 1:43 PM by Paragon failed today, 8/16/2016, and was stated as:

"http://neren.rets.paragonrels.com/rets/fnisrets.aspx/NEREN/login?rets-version=rets/1.7.2".

Based on other information provided, the following modified logon apparently did work:

"http://neren.rets.paragonrels.com/rets/fnisrets.aspx/NEREN/login?rets-version=rets/1.8".

Generated was the content [userid and password redacted]:

<rets replycode="0" replytext="Login Request"><rets-response> Info=USERID;Character;[usedID redacted] Info=USERLEVEL;Int;1 Info=USERCLASS;Character;21 Info=AGENTCODE;Character;279144 Info=BROKERCODE;Character;4869 Info=BROKERBRANCH;Character;4869 Info=MEMBERNAME;Character;[name redacted] Info=MetadataVersion;Character;16.8.17085 Info=MetadataTimestamp;DateTime;2016-08-11T20:45:11.5Z Info=MinMetadataTimestamp;DateTime;2016-08-11T20:45:11.5Z Info=TimeoutSeconds;Int;0 Info=VendorName;Character;Black Knight MLS Solutions Info=ServerProductName;Character;RETS-Paragon Info=ServerProductVersion;Character;1.0 Info=OperatorName;Character;New England Real Estate Network GetMetadata=/rets/fnisrets.aspx/NEREN/getmetadata GetObject=/rets/fnisrets.aspx/NEREN/getobject Login=http://neren.rets.paragonrels.com/rets/fnisrets.aspx/NEREN/login Logout=/rets/fnisrets.aspx/NEREN/logout Search=/rets/fnisrets.aspx/NEREN/search </rets-response></rets>

It appears that the Paragon is changing systemic functionality [in this case- version number] without notification which caused the above anomaly. If the absence of such notifications persist, such will frustrate vendor testing the InnoVia to Paragon conversion, which is exacerbated by the lack of InnoVia to Paragon conversion documentation.

Referring to the original question which has not been resolved, and notwithstanding whatever RETS version InnoVia currently uses, the following Innovia search does indeed work:

"http://nne.rets.mlxinnovia.com/nne/Search?SearchType=Office&Class=Office&Select=FirmID,OfficeID,OfficeName&Format=COMPACT-DECODED".

This search yields the following results consisting of 4864 records:

"<rets replycode="0" replytext="Operation Successful"> <delimiter value="09"/> <columns>FirmID OfficeID OfficeName</columns> <data>100 0 RE/MAX Black River Realtors</data> <data>1000 0 Mark Stimson Assoc.</data> <data>1001 0 Thompson Appraisal Co.</data> ...snip... <data>9999 0 NEREN</data> <data>9999 1 NEREN Temporary</data> <data>I99999 0 Comp Agent</data> <data>OSIPLI 0</data> </rets>

The search noted in "Answer #1" from Paragon above does not work: "http://neren-rets.paragonrels.com/rets/fnisrets.aspx/NEREN/Search?SearchType=Office&Class=Office&Select=O_BranchOfOrgID,O_OfficeID,O_OrganizationName&Format=COMPACT-DECODED&rets-version=rets/1.8"

The error message is:

"Server Error 412 - Precondition set by the client failed when evaluated on the Web server. The request was not completed due to preconditions that are set in the request header. Preconditions prevent the requested method from being applied to a resource other than the one intended. An example of a precondition is testing for expired content in the page cache of the client."

I would appreciate a Paragon example solution that actually works relative to a current Innovia very basic database interrogation.

edit flag offensive delete link

Comments

You can still use RETS/1.5 but we are trying to move people to newer versions either 1.7.2 or 1.8 wherever possible.

bwolven ( 2016-08-16 10:15:30 -0500 )edit

Version 1.7.2 apparently is not a valid option. I could not log in with it. Why did the search interrogation fail and generate the error message: "Server Error 412"? What is the correct syntax to generate the 4864 NEREN "office" records?

dcgllc ( 2016-08-16 10:40:58 -0500 )edit

I checked, and your account profile allows access to ActiveOffice resource not Office resource. RETS/1.5, RETS/1.7.2, and RETS/1.8 are all valid options. RETS/1.8 is the only one that allows an empty search "Query" parameter. For earlier versions you must provide a valid Query.

bwolven ( 2016-08-16 13:37:54 -0500 )edit

I modified the search changing Office to ActiveOffice: http://neren-rets.paragonrels.com/ret.... It does not work.

dcgllc ( 2016-08-16 14:27:15 -0500 )edit

add a comment

answered 2016-08-15 08:48:53 -0500

bwolven

http://paragonconnect....

updated 2016-08-16 16:15:15 -0500

The equivalent Paragon RETS search would be: "http://neren-rets.paragonrels.com/rets/fnisrets.aspx/NEREN/Search?SearchType=Office&Class=Office&Select=O_BranchOfOrgID,O_OfficeID,O_OrganizationName&Format=COMPACT-DECODED&rets-version=rets/1.8"

Calling search without the Query wasn't supported until RETS/1.8.

Updated 2016-08-16 - 15:20 CST:

I did see an entry in our log for your last attempt. But it was a search request without doing a login request first so it failed.

I used the following steps in a browser window:

"http://neren-rets.paragonrels.com/rets/fnisrets.aspx/NEREN/Login?rets-version=rets/1.8"

"http://neren-rets.paragonrels.com/rets/fnisrets.aspx/NEREN/Search?SearchType=ActiveOffice&Class=ActiveOffice&Select=O_BranchOfOrgID,O_OfficeID,O_OrganizationName&Format=COMPACT-DECODED&rets-version=rets/1.8"

"http://neren-rets.paragonrels.com/rets/fnisrets.aspx/NEREN/Logout?rets-version=rets/1.8"

With your account and it returned the office data.

Updated 2016-08-16 - 16:20 CST:

I saw the search come over in a browser request and it looked like it worked properly.

With your PHRETS/1.0 attempt afterwards, it looks as though the URL Query parameters are getting jumbled up.

Here is your last search request:

"SearchType=ActiveOffice&Class=ActiveOffice&Query=%28%28Search%3F%0ASearchType%3DActiveOffice%26Class%3DActiveOffice%26Select%3DO_BranchOfOrgID%2CO_OfficeID%2CO_OrganizationName%26Format%3DCOMPACT-DECODED%26rets-version%3Drets%2F1.8%0A%29%29&QueryType=DMQL2&Count=1&Format=COMPACT-DECODED&Limit=30000&StandardNames=0"

Here's what it looks like decoded:

""SearchType=ActiveOffice&Class=ActiveOffice&Query=((Search? SearchType=ActiveOffice&Class=ActiveOffice&Select=O_BranchOfOrgID,O_OfficeID,O_OrganizationName&Format=COMPACT-DECODED&rets-version=rets/1.8 ))&QueryType=DMQL2&Count=1&Format=COMPACT-DECODED&Limit=30000&StandardNames=0""

edit flag offensive delete link

Comments

Thank you for the Paragon equivalent of the Innovia search request. I have no documentation that would have led me to the conclusion that "&Select=FirmID,OfficeID,OfficeName" translated to: "&Select=O_BranchOfOrgID,O_OfficeID,O_OrganizationName"

dcgllc ( 2016-08-17 08:30:53 -0500 )edit

Regarding the text above after: "Updated 2016-08-16 - 16:20 CST", this search request was generated under program control [phRETS'] using invalid arguments, thus is irrelevant to resolving the original problem.

dcgllc ( 2016-08-17 08:34:12 -0500 )edit

add a comment

InnoVia to Paragon Conversion: Queries Fail To Produce Field Data

2 Answers

Comments

Comments

Question Tools

Stats

InnoVia to Paragon Conversion: Queries Fail To Produce Field Data edit

2 Answers

Comments

Comments

Question Tools

Stats

InnoVia to Paragon Conversion: Queries Fail To Produce Field Data