| Button handy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
One of the main benefits of SIL is, that scripts are portable across instances and hosting types. This is possible because the SIL language was created to run at a higher level then a general programming language. It was built to be similar to a domain specific language that simplifies the scripting process. The language attempts to remove the unnecessary complexity of the technical implementation details without removing the power of a scripting solution. So if you wrote a SIL script in an older version, it will work in any future version, and you can migrate your script from Server to DC to the cloud without having to rewrite any scripts.
...
| Info |
|---|
How can I reduce the number of changes?Use SIL aliases - by using SIL aliases you avoid using the custom field ID directly in the script to protect your script from changes. Clean up old projects prior to migration - make any necessary project changes in your familiar environment rather than dealing with them in the new and unfamiliar cloud setting. Use migrations tools like CMJ - Did you know that Power Scripts is compatible with the Configuration Manager Cloud Migration Tool? Well, it is! Configuration Manager helps analyze and report changes, so that they can be resolved prior to the migration. |