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.
This article discussed about the Alteryx Connectors deprecation, for initial set of connectors, and clarifies the questions around the Connectors deprecation.
This document explains the steps to export HAR files by using Chrome Developer Tools built into Designer to investigate the interface of HTML GUI SDK tools.
This article explains how to troubleshoot and resolve the error "You have found a bug. Replicate, then let us know." when using a Python-based connector
When trying to create a temporary table for use in the Data Input Tool (connecting to Google BigQuery) the workflow errors out with "Executing PreSQL: CREATE OR REPLACE TEMPORARY TABLE... Invalid query: Use of CREATE TEMPORARY TABLE requires a script or session"
This article includes the steps needed to obtain the Client ID and Client Secret from the Google account. This is to be used for the Optional OAuth2 Overrides option on the Alteryx Google Sheets connector.
Latest versions of the Google Sheets and Google Analytics Connectors introduce ability to share a Connection Token across tools helping to stay under refresh token limit
Connecting to Google Analytics is becoming more and more popular. There are a few things you need in order to use the Google Analytics macro; a Google Account (e.g., Gmail) and authorized access to an existing Google Analytics account. This article will help you get the rest of the way.
If you observe an error message like Error: Salesforce Input (1) File " ", line 1 os.environ['PATH'] = r"... please read on to learn how to adjust the environment variables to resolve it. This can happen with any one of several Connector tools, not just the tool mentioned in the example.
ERROR: "Could not build wheels for cryptography which use PEP 517 and cannot be installed directly" while installing OneDrive tools in Alteryx Designer
Leading Zeroes Removed When Writing String Data to Google Sheets
When writing string data to Google Sheets that contain leading zeros, the leading zeros are removed after being written to Google:
Environment
Product - Alteryx Designer
All Versions
Product - Google Sheets
Diagnosis
Google automatically formats values when they are written to a cell. The same behavior occurs when manually entering data into the sheet directly. When looking at the web traffic, one can see that the following is sent to Google from Alteryx:
<batch:operation type="update"/>
<id>https://spreadsheets.google.com/feeds/cells/1YW6I6543216gsgsgsgsgD24j-hHA6ydcA/od6/private/full/R4C1</id>
<gs:cell row="4" col="1" inputValue="00004"/>
The correct value "00004" appears as the InputValue. Google then returns the following:
gs:cell [ row=3 col=2 inputValue=4 numericValue=4.0 ]
Google has interpreted "00004" as a number and automatically converted it to "4."
Solution
You can workaround this by placing an apostrophe in front of the value within Alteryx prior to writing the data:
This forces Google to interpret the data as a string and include the leading zeroes. The following is a sample formula that adjusts all rows within a field to include a leading apostrophe:
"'" + [Field1]
Additional Resources
Google Sheets Output Help Documentation