Short answer – no.
Long answer:
The way eaDocX works is that it creates tables by reference back to the original element – in your case the Actor.
Each column in the table is then created with reference to that Actor: either a single-hop relationship, or a multi-hop one, but it all starts with the ‘source’ element.
The problem you face is not unusual for a complex model. The simple solution, which I admit isn’t exactly what you want, is to have multiple tables, and use eaDocX hyperlinking to join them.
So, a table of Actors and their Activities, with each Activity being a hyperlink to…
then
…elsewhere in the document,
A table of Actvities, and the Application Components they are linked to. And even a link back to the actors.
Alternative is to use multi-hop, and show all the Application Components for the Actor.
The hybrid which you’re asking for, which would be a MUCH more complex table (rememeber it has to work for any possible model structure) , with some cells being split, has proved too complicated to implement.
