error when importing a postman collection
SOLVED- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
error when importing a postman collection
I tried to import a postman collection (JSON format) in SoapUI/ ReadAPI, but I encounter the following error:
net.sf.json.JSONException: JSONObject["requests"] is not a JSONArray
Can someone please help me?
Solved! Go to Solution.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
How to report to support team?
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I have raised ticket for this.
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
thank you!
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any update on this? I have the same issue.
