Can you please suggest a workaround for Exporting connections from Version 22.214.171.1247 and import into Version . . .
Sure - recreate the connections manually using the info you find either in the exported file or in the connection dialog of version 18.x
i have more than 100 connections which is why i am looking for an alternative method of exporting and importing.
Manual is always default option.
I guess the JSON format was supposed to be an improvement, but there is no provision for backward compatibility. That seems reasonable since your use case seems atypical. You might try a JSON-to-XML converter, as in
Thanks Glen i gave it a try but unfortunately sql developer Version 126.96.36.199 is not accepting the converted version of JSON to XML.
After browsing the required .xml file as input the "next" button does not work.Also i compared a regular exported xml file to the converted json to xml file and found the format to be different and
may be thats the reason it wasnt accepting the converted one.
1 person found this helpful
Thanks for the feedback. Yeah, the extra levels with all those extra tags in the XML for the earlier versions make this idea a complete non-starter.
But since the app doesn't accommodate the different formats there isn't really an alternative except to do it manually - which confirms they got created correctly, or try to manually convert the data in which case you are taking substantial risk of error.
You are already taking substantial risk if you are keeping the passwords for 100 connections in one place like that. Pretty easy for someone to do an analysis and determine which systems are using the SAME password.
Open up a copy of 18.1 or 17.x if you still have it and see if you can export from there.