Bug: exporting Requirements with Build 799

[Hans-Christian]

Hi I have a RTF-Template like the following:

package >
{Pkg.Name}

element >
Status : {Element.Status}
Version: {Element.Version}
{Element.Name}
file >

{ElemFile.FilePath}
< file

< element
child packages >
< child packages
< package

Since last version is worked correctly and the linked files are exported via ElemFile.FilePath. Now with the new Build 799 most exported Requirements have the text "{ElemFile.FilePath}" instead of the file path! But my model is the same as before and the template, too.

Does someone also can see a behaviour like this ?

Regards
Hans-Christian

[mark.myers]

Yes, I am getting exactly this problem - I'm on Build 806.
I will ask Sparx...

[«Midnight»]

Out of interest...

Have you tested this with 810 (7.0 beta 1)?

I'd do so, but I don't have a model handy with the correct characteristics - or perhaps I just don't have my RTF generator tweaked the way you do.

David

[mark.myers]

Hi David.

No I haven't tried with 810.
I haven't wanted to use it yet as it is Beta.  
I am wanting some of the features in it though so maybe I should bite the bullet.
Can you have side-by-side versions? (in case it messes something up)

[«Midnight»]

Yes Mark, but I don't know all the implications.

There is a post from sometime in the prior two weeks or so that tells you what to do.

Still, perhaps somebody else out there has the necessary configuration to give us an answer.

David

[mark.myers]

I have tried this in Build 810 and it is fixed.

I have also found a work-around for those still using 806 (as I am in production).  If you have a "model document" section in the template - it can be empty - then the ElemFile fields will work.

[«Midnight»]

Nice workaround Mark.

Not really elegant I suppose, but effective!