Sign in to join the conversation:
Hey everbody!
Is there a way to show the automatically generated number which will be created by the new form, on that form?
I hope I have written that understandable.
Kind regards,
Florian
Hi Florian,
Unfortunately, it isn't possible because Smartsheet creates the automatic number after the form is submitted. A possible workaround that could work but it depends on your specific use case. You could have Smartsheet automatically send out the number afterward with the help of Alerts & Actions.
Would that work for you?
I hope this helps you!
Best,
Andrée Starå
Workflow Consultant @ Get Done Consulting
Another proven work-around:
Based on this post:
http://ronin-global.com/2018/07/20/defaulting-to-a-date-in-a-smartsheet-webform/
Skip the discussion on Method 1.
This is easiest if your AutoNumber is just a number (displayed) -- ie 003 not AA003. You'll need to convert the AutoNumber to a Number (using VALUE()) and then get the MAX() + 1 for that (as a number) and create the URL as discussed in the post.
Several (major) limitations to this, but many of them can be resolved. Since the URL is dynamic, users can't just click on the link they got last week.
Craig
For our workflow it was just "nice to have" and not mandatory.
So we`ll think about it.
Thanks a lot for your help guys, appreciate that!
Happy to help!
I have tried to set them as Edit - can share, Edit - cannot share, and commenter and nothing works, they cannot add data to the sheet. Does anyone have a solution?
The Issue My project-specific metadata sheets use INDEX/MATCH formulas that reference the Intake sheet using a Project ID. When the automation archives rows from the Intake sheet, these formulas break because they can no longer locate the source data. Example formula: =INDEX({Project Intake Name}, MATCH([Project ID 1]@row,…
Two of my five automation workflows appear to have just randomly stopped performing on April 9, 2026. All others, which would/are performing as normal and would be functioning alongside the other workflows, are functional and appear to be untouched by this 'bug'. Help I've tried all that I can think of.
