To connect to our IBM DB2 database, we need to set a custom "packageCollection" value as an additional connection property in a copy activity. However, when inspecting the pipeline's JSON, ...
We’re experiencing the same issue on our tenant as well, the “packageCollection” property is being saved with a trailing space (“packageCollection ”), causing DB2 connection errors. Manually editing the JSON works as a temporary fix for us too. Hopefully this can be addressed in an upcoming patch.