# Deprecating MultiBlock datasets

**URL:** https://discourse.paraview.org/t/deprecating-multiblock-datasets/4950
**Category:** Development
**Tags:** proposal
**Created:** [July 24, 2020, 1:19pm UTC](https://discourse.paraview.org/t/deprecating-multiblock-datasets/4950 "2020-07-24T13:19:41Z")
**Posts on this page:** 1
**Showing post:** 23

<div class="post-metadata">

### Author: ![penkod](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/p/b3f665/32.png) [@penkod](https://discourse.paraview.org/u/penkod)
#### Post date: [July 30, 2020, 7:48am UTC](https://discourse.paraview.org/t/deprecating-multiblock-datasets/4950/23 "2020-07-30T07:48:18Z")

</div>

I worry about backward compatibility for custom plugins as well, as I am extensively employing the **vtkMultiBlockDataSetAlgorithm** and the **MultiBlock inspector** in my own custom ParaView plugins (C++). It would be very convenient, after MultiBlocks get deprecated, to have clear instructions on how to switch to the new classes (the mentioned vtkPartitionedDataSet, vtkPartitionedDataSetCollection or vtkDataAssembly). If this could be provided then the transition might not be so painful then, otherwise, those who heavily use the MultiBlockDataSets, including myself, might remain “stuck” at the older ParaView versions for some time.

---

_[View the full topic](https://discourse.paraview.org/t/deprecating-multiblock-datasets/4950)._