HTML reports - can't click for details on elements

[Mike Hemming]

I am defining my architecture according to the Archimate 2.0 standard.  I’ve created packages for the Business, Application and Technical Architecture models as well as a package for the Viewpoints. The Architecture packages contain all the model elements in subordinate packages (nodes, App services, Business functions, etc)  The Viewpoints folder contains the diagrams showing the relationships between the model elements, i.e. the layered view shows the top to bottom view.
When I generate an HTML report for a given viewpoint, I only seem to get the diagram and cannot dbl click on any element in the diagram to get its propertied, files, links.  My intention was to publish many aspects of the architecture in HTML.
Is there any way to include the elements defined in other packages in an HTML Report? Really difficult to produce useful HTML Reports when they are limited to the elements in the target package (and its subordinates) only. Ia anybody modelling their Archimate models differently?

[Glassboy]

You're making a rod for your own back.

I'd suggest you create a "menu" diagram at the top level and create your HTML report from the top.  That way your package structure can stay the way you want it.

[Dermot]

If the packages containing these elements are not reported in the Package tree that you are reporting then they won't be selectable in the output.
You can do as Glassboy suggests or look at setting up a Virtual HTML report see:
http://sparxsystems.com/enterprise_architect_user_guide/12.1/report_generation/master_documents_and_model_doc.html

[Mike Hemming]

Thanks Dermot and Glassboy.  I haven't gotten back to this for a while, but I did create a Model Document in the particular Viewpoint folder, in this case "Infrastructure/Database Servers" and added packages from the Technical Infrastructure repositories for the Nodes, Services, devices, artefacts, etc.  Worked pretty well.  I'm a bit worried about producing reports for a layered viewpoint though, say a view of the applications Intake process.  If I include packages for the application functions, components, services and infrastructure  folders, I'd likely include all of the elements in these packages, not just the elements contained in the layered diagram.
But I may be asking too much.  Maybe I just need to expose the model through the EA reader.  I'll keep pursuing the documentation elements.  Thanks for the lead and the help.