Hi I was using imbedded Snippets but then decided to change the name of one. Well it didn't change the name where it was imbedded and it did not notify me that I could be causing this error. Is there a way to avoid this kind of error happening in the future?
1 Like
Hi Elizabeth! For now, sadly, there is no automatic way to avoid this error. After editing the shortcut of your embedded snippet, you need to:
- manually search (use the search bar in the top right) for occurrences of "import: "
- manually edit every other snippet to point to the new shortcut.
I believe we should have a better (more automatic) handling for this situation 
So I have moved your post to the #ideas category.
2 Likes
I think that embedded snippets should also let the user preview what they contain and let the user edit them from the preview if necessary. Or allow the user to click on them and be taken to where that snippet is for easy editing when needed.
1 Like
LOVE this idea @Elizabeth_Juarez! My teams use a ton of imported snippets. While it is not often we need to change the name of a "source snippet" (the one being imported into a bunch of other snippets), when it does happen, it sure causes a log of issues. This morning I have to change the name of 1 imported snippet which instantly cause errors to be thrown on 63 other snippets that over 100 people were using in that moment. The error reports from my teams came pouring in fast!
Now, I absolutely love how when editing a snippet, if you change the name of a variable, you can choose to have that name change happen for only that specific variable occurrence, or change all occurrences. This enhancement was an absolute game-changer when they deployed it! We sure need this kind of functionality whit comes to snippet naming changes.
Thank you for hearing this TB team - y'all truly rock!
-Brad 
2 Likes