BabaJ

No.
Polygons need a minimum of 3 sides connected in sequence to each other(to be seen as a surface plane). If you 'remove' that edge you are left with only 2 without any connection to each other.

If you set your viewport display to Smooth Shaded you will no longer see that edge.

This is why you might think in other apps they are able to do this, but it's just being hidden from you.

Thanks tpetrick.

Indeed that was 'method' I was looking for (setSelectedWorkItem()).

However, it's a catch 22 to be able to use it.

I have multiple Top Networks, that get accessed outside the Top Networks themselves.

So I created unique attribute names for each Network, e.g. TopNetwork_Name > @pdg_id

I have buttons with callback scripts(On the red null nodes in the example file) that run the python functions in the Python Source Editor.

For testing purposes I split it up into two buttons. The first button(Set Wedge) cooks and outputs the desired work item.

The second button(Set Work Item) I used the setSelectedWorkItem() method to try and select the work item.

However, unless the work item is manually selected, that ID number needed by the method is not available.

Hence the catch 22.

The ID number is actually there when I middle mouse on the work item(but not selecting it) - as I can make note of the number, manually enter that number in the python function and run it - Then it will work.

But that attribute I create of the pdg_id is not available until the work item is selected, so that attribute cannot be passed to the function which in turn does not allow me to use the button(which calls the function) to set the work item as selected.

I've included a scaled down version of my project. The red null nodes is where the button and callback functions reside.

If you don't want the reverse connection/behaviour,
after making the reference, just right click on the parameter and select lock parameter.