You can now use a XML for Plant Scada 2023R2.

Last updated: October 7th, 2025

Description

Author: Chris Cleope
Published: October 7th, 2025

Details:

Aveva has now updated their licenses so we can now use a demo license going forward each month.

See below for the monthly license: (Internal Use only)

Activate via the “Enterprise License Manager”

Give feedback about this article

Recommended articles

[ISS Support Case] Creating a Template from a ViewApp Instance Undetermined

We use IDE (minimally) Recently migrated from 2014 - 2020 R2 SP1. Primarily IDE is used for CheckIn CheckOut of application Have individual templates which get published. Do not deploy, No Galaxy objects. To create a new app they RB and select > new derived template. Have another app they want to create 'derive templates' from. Does not get that option. Wanting to incorporate a level of customization to their process.

[ISS Support Case] Appserver Code to convert a Json string into XML

Im working on integrate a new MES system that return all the data into a Json sting, how can i conver this Json String into XML Format to use the data inside of .NET Scripting ? I know in Nuget https://www.nuget.org/packages/Json.Net there is a dll that can work with this but there is any way that i can integrate this dll into AppServer?

[ISS Support Case] Migration from 2014 R2 to 2023 R2 Sp1 Undetermined

Objective migrate an application from 2014 R2 - 2023 R2 Sp1 Performed transitional upgrade - 2020 Trying to migrate to 2023 R2 SP1 Gets to a certain point sees aaGR started (no more activity 73% in) found a TN - suggested applying a registry update. Applied with no impact. previously had an issue with batch objects (none of those objects were available) Fixed the problem got batch objects working. Migration process question: Does it need communication with batch server during the migration process or is the migration just about converting code and objects? I ask be cause I tested on 3 separate systems and had similar but varying results). At Client site ; experienced migration issues (lots of RED) the batch server is on separate machine. Tried internally with the difference being the batch server was installed locally) the migration 'worked' there (less RED). It was the best progress thus far. Plant: All Servers are running Microsoft Server 2022 and will be using: System Platform 2023 R2 SP1 Batch 2023 R2 Historian 2023 R2 Servers: Galaxy Server Batch Server Historian Server RDP Server The original Plant used System Platform 2014 R2 and InBatch 2014 R2.