On this page:
Table of Contents
...
Possible Reason for Doc Post Failure | Try This... |
---|---|
Connection Timeout |
|
Google Sheets Workbook or Sheet deleted/renamed First Column header deleted/renamed |
|
Google Sheet has a column or sheet set as a Protected Range |
|
Google Sheets has reached the limit of 5000000 cells |
|
Google Sheets or Google Drive API is not enabled |
|
Google Drive folder deleted/renamed |
|
Google Drive folder name set by template that resolves to null |
|
Google Drive folder name set by template that contains an apostrophe |
|
OAuth Token expired | Follow these instructions to regenerate your OAuth token. Then, update your Doc Actions and rules to reflect the new token. |
...
This error can also occur if you are writing to a Google Sheet using a business rule using the deprecated '&updates' parameter, and you have a text or textarea control that gets a value with a comma at runtime. For example, if you are passing a control in the var updateparams rule such as "FullName" and the runtime value entered is "Smith, John" the comma can interfere with the comma-separated update parameters being passed to the Google Sheet. To correct this, please update your business rule to use the '&updatesjson' parameter as described in this documentation.
You may see this error with the additional error status information "This operation is not supported for this document." In this case, check that your Google sheet is saved as a Google sheet and not a .xlxs file. If you have uploaded an Excel spreadsheet to Google Drive, you will need save it as a Google Sheet after uploading. This will change the spreadsheet key, so copy the new key and update your rule.
Invalid String Literal
If you see the error "invalid string literal" when using a business rule to read or update a google sheet, make sure that you have commented out the slashes in your oAuth Code, as in OAuth21\/\/0dqqBnY...
...