How to update a DeviceLink Job after upgrading a TIA Portal version?

If you upgrade your PLC's TIA Portal version to a new major version number (e.g. upgrading from V17 to V18), the archive file extension will change. If you've been backing up a device that you want to upgrade, the new project file must be updated in Source Control and a new Project created in DeviceLink as a result of this. Follow these steps if you've updated a Siemens' PLC that was being backed up via DeviceLink.

1. Add the new TIA Portal project to the repository in Source Control
   1. We recommend deleting the old project in Source Control and adding the new project. It may also be a good idea to create a new Release in the repo at this point.
   2. You will need to add the new Project to both the main branch and the Auto-Commit branch (if applicable) if you want to continue using the same Auto-Commit branch
2. Delete the old Project in DeviceLink
   1. Since there is no way to update the source PLC project file in DeviceLink, you first need to delete the Project that was used to back up the old version
   2. The original DeviceLink Device does not need to be modified
3. Create a new DeviceLink project that points to the new TIA Portal project as the source file
4. (Optional) Delete the old Job in DeviceLink
   1. Deleting the old Job will remove your Job history for the old version of the project (though the commits will still be on the Auto-Commit branch if you were using Auto-Commit)
   2. Don't delete the old Job if you want to retain the history. Just un-schedule it so it doesn't try to perform future backups 
5. Create a new Job in DeviceLink and link to the Project that you just created

You can read more about our Siemens Step7 TIA Portal DeviceLink support in our Documentation.