Importing a json file through managed connections, re-importing due to a change in json file does not let you override the existing naming , making copy(1) of the connection name. any thoughts/enhancements to address this?
I am withdrawing this idea. The process works well enough. If you submit an updated json file, the naming can be the same with an addition character; like 'v2; or whatever. After import, rename back to your original name, since the service calls will have the same name.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
