Migration

In addition to the trick mentioned by @m1b to create a version specific folder to run the script in older scripting engine. You can also use the following statement to set the script engine version from within the script itself

app.scriptPreferences.version = 15.0 //Change the version as per your need

See the following documentation

https://www.indesignjs.de/extendscriptAPI/indesign-latest/#ScriptPreference.html%23d1e336112

The advantage with setting this property is that if you want to use the older engine for just a set of lines of code, you can do so and then reset it to the latest version for other lines of your code. This way you can use the newer API's of the new version in addition to using the older DOM version for some part of your code.

-Manan 

Certainly, always test scripts. I am not sure I see the issue, just install the new version, keeping the old version, and test.

Hi @Jimmy30034971re4d, I think you are saying that you have some old scripts that you are worried won't work properly in Indesign 2022? If that's right, here are some pointers:

1. Nothing really has changed in ExtendScript at all since 2014. Indesign now has UXP, but it isn't really ready for production scripts, so your scripts should stay in ExtendScript for now.

2. However, some things have changed in the scripting API between 2014 and 2022. However, I believe you can make a folder in the scripts folder called "Version 17.0 Scripts" (see the this answer) so maybe you can make a folder called the version Indesign was in 2014 and put your script in there. Indesign apparently can run scripts with old APIs in this way.

So possibly nothing to do, but testing!

- Mark