I am trying to use the automation to send me Slack notifications with a link to the newly added ticket (row).
I have the “master” table, which I will call DB_Table, and a table view of the master table, which I will call “Customer Pending Action.” I tried using the formula below, with Step 1 result being the newly added ticket via form submission. However, when I click the output hyperlink in Slack, I am redirected to the row inside DB_Table and not to the one inside the table view “Customer Pending Action.”
Unfortunately, using OpenRow creates an Action and not a hyperlink, which when translated to the Slack mesage for some reason it just returns a string of ui
Here is how it looks in the Content field of the automation:
So for your use-case to open in a specific view, you can simply replace the thisTable part with that view (write the name of the view in formula editor)
Here’s an article I wrote detailing Coda URLs. This is a little dated, there is a change in the short id’s used from 3 characters to 6 characters and then of course it’s still using the coda.io domain. But the structure and breakdown all still applies.
I did not understand how Coda URLs work, so @Ben_Lee’s article was really helpful. Thank you!
I will write down here how the experiment went:
This formula created a URL, but unfortunately it still redirected to the master table. Thank you, @Christiaan_Huizer, for the follow-up on the issue anyway. Really appreciate it
Thank you for the reply, @Rickard_Abraham. I trust your experiments, so I was puzzled at first when it didn’t work. When clicking on the generated URL, I would get an error saying “Table was deleted.”
Then I realized I had not shared the information that, in my specific table view, I have multiple tabbed views! It did not come to mind when first posting, but after reading your replies, I noticed it should be relevant. I did not test it, but I think Rickard’s formula will work perfectly if the table view has no tabbed views.
After manually copying the link to the card, in the table view, in the correct tabbed view, I noticed that they put the ID of the tabbed view after the table ID.
So I modified the formula to extract 16 characters instead of 6, and it worked!