So I have a workflow that connects to an API and retrieves data from the API
When the workflow was uploaded to the server, It encountered SSL error and couldn't run.
In order to bypass this error, i added python to my workflow to download the JSON data directly and bypass the SSL connection error.
This seems to work, downloaded JSON data seems truncated but with a little research, i found out the data is till in there and no cause for worry
But the downloaded json data never gets completely extracted using the JSON parse tool
I have attached images of the API call on postman and the records returned.
Also attached is the records returned in the JSON parse tool in ALteryx.
The json data in alteryx should be more than that and the entity data should match
what is on post man.
I'd need help with this urgently
Yes I made use of download tool and it worked just fine on alteryx desktop.
But when uploaded to server, I encountered SSL connection error.
Using python was the only work around i know
Is the server behind the proxy? And within Python tool, I assume, you publish to the gallery and it works fine, but truncates number of the records.
The python version works fine on server and yes it does truncate a number of records even on alteryx desk. The JSON Parse tool truncates the JSON data gotten from the python download.
I don't know why this happens
So, considering GIGO (Garbage In Garbage Out), I believe your issue is with Python. Alteryx has nothing to do, and relies on Python's output. I suggest you focus on the Python script.
The python output seems fine. The workflow replaces " ' ", with ' " ' making the JSON properly formatted.
The JSON data sent into the JSON parse tool is correctly organized.
The fact the the Parse tool correctly reads the firs three lines of the python JSON output shows that the python JSON output is fine.
could you post what you see in your browse tool? TBH - I'd look into why you are seeing the SSL error on server - and fix that. If that doesn't work - I'd test your python code on laptop. This is a public api - no? perhaps you can share the resource link...