I'm an curious if the following described behavior is intentional or if it is a bug.
Example:
Say you have 3 groups loaded into the data portal in the following order (note: all three groups contain the same channel names):
[1]/DataSetA
[2]/DataSetB
[3]/DataSetC
You then create two areas in VIEW, both with ChannelTable as the display type.
You then drag "[1]/ChannelA" from [1]/DataSetA group into one area and "[2]/ChannelB" from [2]/DataSetB into the other area.
Then, you decide to reorder the groups in the data portal by moving DataSetC to the top of the data portal - resulting in the following:
[1]/DataSetC
[2]/DataSetA
[3]/DataSetB
Your VIEW layout automatically updates the existing channel tables to make sure that the data you were looking at before changing the data portal remains the same after you change the data portal. It does this by updating "[1]/ChannelA" to "[2]/ChannelA" and "[2]/ChannelB" to "[3]/ChannelB". Everything up to this point seem intuitive to me.
The oddity comes in when you then delete [3]/DataSetB. When you do this, the VIEW layout is changed to show "[1]/ChannelA" and "[2]/ChannelB". This seems a little confusing to me as I was expecting the VIEW layout to continue showing "[2]/ChannelA" and "[3]/ChannelB" and since "[3]/ChannelB" would not exist after deleting it, the VIEW area which contained that area would be blank.
This is not necessarily a huge issue, but did cause me some challenges when dealing with several different data files/group which were similarly named and hard to distinguish between based solely on group name. I was moving and deleting groups in the data portal and didn't realize the VIEW layout was performing this behavior.
Is this the expected behavior? If so, would there be any appetite to update it to my suggestion above?