Skip to main content

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?

Does your second customization project extend the base graph or does it extend the first customization project?


@Django, the second extends the base. Are you going to suggest that I extend the first one instead?  That’s a good idea, but I wonder if the UI controls will still need duplicated.  I’ll give this a try.


The tab is still duplicating on the screen unfortunately.


Do the tabs have the same ID in your two customization projects?  I’m wondering if they were to have different IDs if you’d get two tabs vs having the same ID and thus the merging engine would realize that you are customizing the same tab.


@Django, I had that thought, too, but the IDs are all the same on both tabs.


Hi @Tony Lanzer were you able to find a solution? Thank you!

 


@Chris Hackett Have not resolved yet, no.  Will probably get back to this and look for some kind of workaround soon.


Reply