Post History

Source: https://writers.stackexchange.com/a/33758
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/

Source: https://writers.stackexchange.com/a/33758
License name: CC BY-SA 3.0
License URL: https://creativecommons.org/licenses/by-sa/3.0/

### No, there is no such option

Looking through the [official documentation](https://www.nevigo.com/help/UI_Search.html) and checking the [query language document](https://www.nevigo.com/download/documentation/ArticyDraft%20-%20Query%20Language.pdf) it appears that you can't simply use the advanced query script to write for example a SQL Upate. It only gives you search options and the interface doesn't have a replace option.

### There is a workaround - export to Excel and then import

Looking through the forum I found [this discussion](https://www.nevigo.com/forum/viewtopic.php?f=4&t=1687&p=3295&hilit=replace#p3295) from 2014 where an employee mentioned that adding a replace function is on their agenda... As far as I can see this feature is probably still on the agenda, but I couldn't find more.

You could use the [API](http://www.nevigo.com/en/pricing-table/api/), but far easier, faster and cheaper is the solution to

- Click on the project hierarchy view
- Right-Click on the uppermost hierarchy node (or one of the lower ones, if you only want to replace for example text in the assets or entities)
- Click on `Export` (or press `Ctrl + Shift + E`)
- Choose `.xlsx (for re-import)`
- Click `OK`
- Excel should open; if not, navigate to the file in your filebrowser and open the file
- Use Excel's `Search and Replace` function
- Save the file
- In Articy:Draft click on the upper left bubble to open the bubble menu and click `Import` (or press `Ctrl + Shift + I`)
- Choose the file 
- Keep pressing `Next` until you are back to the normal window

Now all your references should be updated.

Personally I would recommend backing up your project before. Of course you should always backup your project in case something happens, but as this is a workaround and you are manipulating the values outside of the usual environment the chances for making mistakes are probably higher.

I only tested this with a quick test project where I created two entities and a dialogue that had text like "Player" in them and changed every occurence of "Player" in Excel to "Tester". It seemed to work.

Original score: 1