Hi,
Our solution features an extended endpoint (v 18.200.001 Default, System Contract 3) that has grown over the years to contain a lot of crucial elements not expoed in the standard endpoint.
We are wanting to stay with the times and derive from a newer endpoint version (22.2) and we've tinkered with the project.xml file a bit only to get an endpoint that 'sort of' works but not well enough to use. Specifically, the resulting endpoint can't export the swagger definition for building a client.
So my question: Is there an automated means of migrating an extended endpoint to a newer version, or will we have to just export it to Excel and build the new one manually?
Understandably we would prefer, if at all possible, to automate this and mitigate the human element and several cycles of fixing errors.
Thanks!
Mike