@Nimrod_Shalit does a configuration need to be made to enable auto-binding or do the objects need to be in the same workspace but different pipelines (not sure if this is even possible)?
In our case, auto-binding doesn't appear to be happening automatically because we have reports in one pipeline and our datasets in another pipeline as described in the docs, and when we deploy the reports, they retain the connection to the dataset they were already connected to rather than auto-binding to the new dataset (i.e., report connected to TEST dataset, when report deployed to PROD, the report retains connection to TEST dataset rather than updating to PROD dataset).
Even if auto-binding can work, it would still be better to explicitly set a parameter variable to define the connection - in some cases, we need to use a variable, in other cases, we may want to explicitly set the connection directly to an dataset without a variable regardless of pipeline stage (eg. confirm that a report works with the PROD dataset while the report is in TEST stage before deploying to PROD stage).
