Just to follow up…we were using Model View as a way to filter elements that belong to a particular project (we are using a Tagged Value to assign a project number to an element). Our requirements are not usually documented within a single project package – instead, we are trying to mainting a holistic model of our entire production enviroment, and add to it as time goes on (rather than have our requirments chopped up into a buch of separate project doucments). Using the tagged values allows us to attach a project number to an element, and add notes describing what change was made. Trying to identify elements spread across a huge EA model is a pain in the a$$, which is why we use a Model View to create a filter and only look at elements with Tagged Value = to ‘Project X’. Once our model view is created, we were hoping to just insert elements from the model view right into eaDocX. In the meatime, if you have any other suggestions on how we might be able to accomplish our original intent (pull in a wide array of elements that are scattered throughout multiple packages within a large system model), we’re open to anything!
Thanks!
