The order does not change when I reconfigure them, and I also tried to manually change the order of appearance in InitializeComponent() as well as restarting Visual Studio without effect. Could there be some kind of file-based caching in the designer that has cause the ordering to "freeze"?
In the report I am currently working with, I am fetching results from a time series database into a large table. I have an individual object data source for each cell, as my API require several parameters for each call - like fetch type and ID of the involved time series.
The challenge with fetching data for multiple cells in one data source is that it would be difficult to handle all the required parameters. Hard coding tailored Business objects is currently not an option. One reason for this is that there will be customization of the report for different clients that would require adding or removing some of the cells, as well as the ID for the time series are likely different in different environments where the report will be destroyed.
So back to the starting point, I think improved listing of data source components would be the best solution for me. Or alternatively a way to assemble multiple API calls into one data source - something similar to linking entities into one query. But I guess this would be far more complex to implement, unless it is something already being worked on.