Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
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 noticed that "packageCollection" is added with a trailing space ("packageCollection "). This causes issues, as the DB2 database doesn’t recognize the property correctly.
Manually removing the space in the JSON makes the pipeline work again, so for anyone facing the same issue, that’s a temporary fix. But ideally, this bug should be resolved at the source.
Is this the right place to report such a bug? As it stands, fixing it manually means the property can’t be configured through the UI anymore.
Solved! Go to Solution.
Hi @TimoW ,
Thanks for posting in Microsoft Fabric Community.
Based on your findings it does look like the property is being written with a trailing space in the JSON, which explains why DB2 does not recognize it. Editing the JSON manually is a valid workaround for now, but as you mentioned, it prevents further changes through the UI.
Since this is product-side behavior, the right next step is to log it in the Fabric Issues forum here: Issues - Microsoft Fabric Community
That way it can be tracked by the product team. If this is blocking for your environment, you may also consider opening a support ticket so it can be investigated directly.
Please reach out for further assistance.
Thank you.
Hi @TimoW ,
Thanks for posting in Microsoft Fabric Community.
Based on your findings it does look like the property is being written with a trailing space in the JSON, which explains why DB2 does not recognize it. Editing the JSON manually is a valid workaround for now, but as you mentioned, it prevents further changes through the UI.
Since this is product-side behavior, the right next step is to log it in the Fabric Issues forum here: Issues - Microsoft Fabric Community
That way it can be tracked by the product team. If this is blocking for your environment, you may also consider opening a support ticket so it can be investigated directly.
Please reach out for further assistance.
Thank you.