Tom Tomasovic

[Tom Tomasovic]

You got it. Thanks! Tom

[Tom Tomasovic]

Diagrams are truncated as they are being inserted into the document (in draft).

[Tom Tomasovic]

Okay!

I have completed my investigations, and here are the results…

Environment 1-
eaDocX = 3.5.9.7
EA = 13.0.1310
Office Pro Plus 2010 = v14.0.7194.5000

Environment 2-
eaDocX = 3.5.9.7
EA = 13.5.1352
Office Pro Plus 2013 = v15.0.5015.1000

The repository for both environments is the same.

If I generate the document in E1, all is well.
IF I generate the document in E2, the diagrams are truncated.
If I generate the document in E1 and open in E2, all is well.
If I generate in E2 and open in E1, the documents are truncated.

My hypothesis is that the issue is with generating the document in Office 2013. What is really irritating (and amusing) is that, as the document is being generated in E2, I can see the diagrams correctly. However, once the document is fully generated, they are truncated. One more thing I may try is to generate a draft version of the document to see if the issue is when the cross+references and links are created.

Not sure if this information is useful for anything, other than preventing someone else from tearing their hair out trying to diagnose a weird problem. If anyone has other thoughts or input, I’d certainly be interested in seeing/hearing it.

[Tom Tomasovic]

Doesn’t seem to be relevant. Just another “variable” I thought might bear investigating. It’s just a different way of looking at the content. For others (who might be having issues with diagram size), it might be useful.

[Tom Tomasovic]

Web Layout in Word.

Just regenerated my document from another installation (same database), and everything seems fine. Tracking down information on versions (EA, eaDocX, Word), but don’t have all the info yet.

[Tom Tomasovic]

😛 👿

LOL!

Tom

[Tom Tomasovic]

Hi David,

The best I could come up with would be to start the extract from the most granular level and work back to the higher levels. I.e., if you have an element which has several related values associated with it, start from the related values, extract them and then relate them to the parent element.

Hope this helps!

Tom

[Tom Tomasovic]

Works for me.

I was advised to keep the package structure as “flat” as possible, and I am finding that does not work particularly well in many cases. In this case, I have a product which covers business processes, which are realized by use cases (and requirements, etc.). Package structure should probably be Product>>Processes, Product>>Use Cases.

I will see what I can dig up on the element profiles, since I don’t recall them showing up for BPMN Processes, but, then again, I might not have added a process as a specific element to the document. Anyway, I will give that a try.

Thanks!!

Tom

[Tom Tomasovic]

Looks like I was doing something wrong. Today, my layouts are being preserved, and I can open the file and import/export the way I want to.

Tom

[Tom Tomasovic]

Okay…

Need another clarification.

I have created an Excel extract, and what I would like to do is to be able to delete all the data rows from the extact, preserving the headings and the column layout. I may be doing something wrong but, when I try this, my column layout is gone (in the profile area of eaDocX). It seems to revert to a “default” layout. When I export again, the file has the default column layout with a previous set of selected columns.

How do I get eaXl to preserve my column layout so that I can reuse the file?

Tom

[Tom Tomasovic]

I kind of thought that was the way it would work. I can retain my validations in a separate spreadsheet (template) and cut and paste rows from the eaDocX extract into the template. If necessary (likely), I can reapply the validations after copying in the export.

Thanks!

Tom

[Tom Tomasovic]

Actually, with a little more investigation, I appear to have found the way to make this work.

Sorry for bothering!!

Thanks!

Tom

[Tom Tomasovic]

In this particular case, there seems to be an issue with the formatting, independent of any style overrides.

Given several issues with document formatting, it looks like we can’t really use eaDocX for at least one of the documents we want to generate. Given other issues (related to Issues and Tasks covered in other posts), other potential uses are also questionable.

Overall, not a promising prospect!

Sorry!

Tom

[Tom Tomasovic]

Either I don’t understand your premise, or I don’t agree with it. I can’t see any reason why a user would want to look at a list of 24 items and be forced to realize that it’s actually only 12 repeated twice, particularly if they are all formatted identically.

That’s the issue I was dealing with.

As I think I reported, this seems to be specific to the Package element and, in that case, it’s pretty easy to accommodate, once you know what’s going on.

[Tom Tomasovic]

I think I found this one on my own. (;-}

Tom

[Author]

Posts