This site uses different types of cookies, including analytics and functional cookies (its own and from other sites). To change your cookie settings or find out more, click here. If you continue browsing our website, you accept these cookies.
I have a few problems relating to the output of the Alteryx Twitter Connector, hopefully someone more familiar with the workings of the connector can help explain why.
1. I'm getting what appears to be a copy of the TweetBody coming through into the TweetID column more often than an actual TweetID (see image) should this happen?
2.There is also multiple rows for the same TweetID
2. When I attempt to parse the TweetBody column it causes the Alteryx JSON Parser to fail with "Error: Designer x64: The Designer x64 reported: InboundNamedPipe::ReadFile: Not enough bytes read. The pipe has been ended". Without the JSON Parse tool the workflow will run through to completion.
3. The description for the connector says that it only returns tweets from the last 7 days, however I'm seeing Tweet posted timestamps stretching back to 2009.
The updated Twitter Search tool is now available in the Data Sources District. The previous version that shipped with Alteryx will be deprecated in the upcoming release (and therefore will be removed from the tool palette), but in the meantime once you install this tool you will see both versions side by side in the tool palette. To remove the previous version click the + (plus) symbol on the far right-hand side of the tool palette, navigate to the Connectors category, and uncheck the first Twitter Search tool.