Column Name references in automation message change to INVALID COLUMN when sheet saved as new

mark.maritch106446

New issue observed when saving as new (or template) sheet with automations using column name tags. All column tags in all automations go to INVALID COLUMN on new sheet.

Simple test with one automation, one column name reference (Comments) works in main sheet but changes when sheet is saved as new.

Anyone else see this ?

Thanks.

ahumpherys

Hey @mark.maritch106446 - I just got the below update from Smartsheet Support in response to the ticket I submitted. Sounds like this is now a known issue and will hopefully be fixed soon!

"I was able to test and reproduce the issue you are seeing. We have engaged our engineering team to further investigate this behavior. We currently don't have an ETA on resolution, but we will reach out as soon as this is resolved. In the meantime, please edit the workflows if needed."

Georgie

Hi @mark.maritch106446 and @ahumpherys,

I’ve reached out to Support and confirmed this issue is caused by a bug and our Product team is working on a resolution. We are not able to provide a time-frame on how long the resolution could take but we are doing our best in order to have this fixed as soon as possible.

Thank you @ahumpherys for updating this thread with the response you received from Support!

Thanks,

Georgie

ahumpherys

@mark.maritch106446 I think we're having the same issue, see my question/screenshots here: https://community.smartsheet.com/discussion/139912/invalid-column-error-in-alert-someone-automation?utm_source=community-search&utm_medium=organic-search&utm_term=invalid+column

ahumpherys

Hey @mark.maritch106446 - I just got the below update from Smartsheet Support in response to the ticket I submitted. Sounds like this is now a known issue and will hopefully be fixed soon!

"I was able to test and reproduce the issue you are seeing. We have engaged our engineering team to further investigate this behavior. We currently don't have an ETA on resolution, but we will reach out as soon as this is resolved. In the meantime, please edit the workflows if needed."

Georgie

Hi @mark.maritch106446 and @ahumpherys,

I’ve reached out to Support and confirmed this issue is caused by a bug and our Product team is working on a resolution. We are not able to provide a time-frame on how long the resolution could take but we are doing our best in order to have this fixed as soon as possible.

Thank you @ahumpherys for updating this thread with the response you received from Support!

Thanks,

Georgie

vgautam

I have been facing this issue as well when I create project workspaces from the blueprints. This has started coming up recently. When is this expected to be resolved?

Georgie

Hi  @mark.maritch106446, @ahumpherys and @vgautam,

I have reached out to the Support team and can confirm this bug has now been resolved.

Thanks,

Georgie