Andy Johnstone

[Andy Johnstone]

Lovely!

Working now.

Thanks people,

Andy

[Andy Johnstone]

Please note: this method is successfully bringing in requirements which are “realised” by the Use Case, I just haven’t been able to get the “tagged value” list to populate to allow me to include them…

[Andy Johnstone]

Hi team,

I’m running 3.2 beta and I’m sorry to say, that I’m still not seeing tagged values.

Can you please refer to the initial message on this thread and see if you can make this work at your end?

Andy

[Andy Johnstone]

The work-around is simple, add a space before the first word, and it is picked up!

[Andy Johnstone]

Ah! I can see the problem, words at the beginning and end of sentences won’t have a leading or trailing space…

It is a very useful function. I’m using for documents which have no other EA content, but the glossary.

:laugh:

[Andy Johnstone]

Here we go.

The cell contains a row of words with no separators…

Bail CCTV CGTF Charge CIB

The values CCTV, CGTF and Charge have been selected, Bail and CIB have been missed.

Hence it’s looking like the first word, and last word (of a set of words in a cell) are being skipped by the routine.

Andy

[Andy Johnstone]

Good morning Adrian,

I think this must be different set of circumstances.

The information has been in the project glossary for a long time, 12 months or more.

Within the document, there is a word table.

A single cell contains a list of abbreviations: ABC, DEF, GHI

When I update the document in eaDocX only the term DEF is found and appears in the generated glossary.

If I change the sequence of the abbreviations to: DEF, GHI, ABC, now only GHI appears in the glossary.

I’ve just tried changing the content in the document so that there are a lot more words in that single cell, now two out of three out of four possible glossary items have been picked up…

I’ll see if I can generate a simple example.

[Andy Johnstone]

Thanks for that, much appreciated.

I’ll make a habit of including screenshots in the future.

🙂

Andy

[Andy Johnstone]

Thanks for that, much appreciated.

Definitely one to avoid if I can. Closing eaDocX didn’t seem to be available, probably because of the dialog conflict. I’ll see if I can find a way to prevent (or at least identify) that one.

I’ve been editing the documents outside of eaDocX because updating fields in Word via eaDocX seems to be causing stability problems. (These are custom fields which identify the document version, version date, project etc.)

[Andy Johnstone]

Further info:

There was a hidden modal dialog spawned by MS Word which I couldn’t find, because the modal dialog in
EA was preventing me from navigating it.

I only found that one, because it was revealed by forcing EA to close through program manager.

Two MDs fighting for supremacy?

🙂

[Andy Johnstone]

Please note, once this dialog has been spawned, there appears to be no way to correct the problem. Unlocking the file does not clear the error condition in eaDocX

[Andy Johnstone]

Nice!

Much better, thank you!

[Author]

Posts