Forum Discussion
13 Replies
- avidCoderSuper Contributor
I have imported your file which you have enclosed with the problem. Seems like, there is no problem with the JSON file. It works fine. Below is the screenshot after I imported the JSON. Try using latest version of postman.
- jlrunningOccasional Contributor
Thanks for replying. sorry I didn't mention it clearly. I mean I was trying to import the postman collection file in the SoapUI or ReadyAPI via File/Import Postman collection. Both of them give the error.
- jlrunningOccasional Contributor
there is no problem if I directly import in Postman.
But I suppose the importing should also work in SoapUI since there is the function called "Import postman collection" in SoapUI.
- avidCoderSuper Contributor
This is probably a bug, Please report to the support team. I tried with different collection file also, same error is coming up for me also. Log a ticket for that.
- jlrunningOccasional Contributor
How to report to support team?
- avidCoderSuper Contributor
This is the link :- https://support.smartbear.com/message/?prod=ReadyAPI
- avidCoderSuper Contributor
I have raised ticket for this.
- jlrunningOccasional Contributor
thank you!
- harshjainNew Contributor
I found a workaround by exporting the Postman Collection as Collection v1 (deprecated). However, authorization credentials are not imported in this way and you have to manually enter and save them in Soap UI requests.