What is the challenge? |
Existence of Smartsheet "system fields" cause error for the first time sending Aha record to Smartsheet, even if the system fields are not used in the mapping. System fields for example:
Error msg example: Field error: Cannot update column '' (CANNOT_UPDATE_CELL: cannot update cell in system column with id: 227036816428932) |
|---|---|
What is the impact? |
Impact: Unable to send Aha record as a new row in Smartsheet if system fields exist in the integrated sheet.
The field is a unique identifier of each row in Smartsheet sheet that we cannot remove, but keeping the field will cause integration error when sending a new Aha record to Smartsheet. If we workaround by removing the field, reloading integration configuration, and then add the field back, the number assigned to the field will change. It impact the ID reference for the whole organization.
For the issue of the rest of the system fields, we are able to workaround by removing “Created by/Created date/Modified by/Modified date” from the sheet, reloading the integration configuration, adding those fields back to the sheet again, and then the integration issue can be resolved and the value in those field will still remain the same. |
Describe your idea |
We regard this as a bug that should be fix. |
Unfortunately, this is also a Smartsheet limitation. We will leave this idea open in the event that we're able to resolve it in the future.