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.
As it stands, fixing it manually means the property can’t be configured through the UI anymore.
- Ghoom on: Azure Maps Controls -> Selection Greyed out
- RobSt on: Error：Visuals display blank when export report to ...
-
hb380
on:
New Button Slicer: Issue with the Grid type of Arr...
-
mattlee
on:
List Slicer Button Dimensions Ignored in Service
-
bhalicki
on:
BUG: report connected to deleted semantic model ca...
- Annamarie on: PBI Semantic Model missing
- Ghoom on: Azure map bubble chart is very blurry
-
JoshT
on:
Deployment pipelines don't support M365 groups
-
Hongju_Jung
on:
A Typo about Measure tools (Korean)
- jwulffraat on: In the Power BI web version, the left border canno...