Picture this: One customization package adds a custom UI tab with grid and underlying view via graph extension. A second customization needs to extend it by modifying the view and adding a new joined column to the grid.
The problem: The custom tab needs added to the second customization package with a grid to make the change, and the result of publishing is that two of the same tab appear on the screen with different grid contents, because merging of a tab is problematic with the UI publish.
I understand that modifying the first customization instead of adding a new customization would resolve this, but in this particular scenario, the first customization shouldn’t change for one instance, but for another it should.
Any ideas for handling this?
