Skip to main content
Hi Guys, yu, its met again.

 

 

I have a question.

 

 

 

If i do this

 

$(DestDataset_CSV)  as a scripted parameter and tcl script:  $FME_MacroValues(Outputdir)\\\\$FME_MacroValues(csv_name).csv (just a simple concatenation)

 

 

Then $(DestDataset_CSV) ends up like  Outputdir\\csv_name

 

the extension is missing.

 

 

Only when i add this extension to $FME_MacroValues(csvl_name) =filename.csv

 

i get Outputdir\\csv_name.csv wich is correct.

 

 

Why is this?

 

 

(in this case i wanted the user not to have to enter the extension, though i changed my mind on that point already..;)

 

 

Also i have boiled down the issue by Robbie B

 

Creating dynamic attributes per "fme_basename"

 

to just this

 

 

 

 

 

 

 

It consist of 3 workspaces, 2 of wich have callers, an intricate parameter construction, 2 startups and one shutdown script.

 

Now one can pick a directory and read files and their attributes straight to (in this case) excell.

 

I think this workspace might inerest you all because it shows a workaround on the issue of dynamic attributes. No exposing is required.

 

 

Check out Robbie B's question jun 18

 

 

Hi Gio, sounds strange. I was not able to reproduce such a situation - FME 2014 SP2.

 

How about requesting Safe support with the workspace reproducing the problem?

 

Takashi
Hi Takashi,

 

 

The issue is in fme2013 sp2.

 

 

We have tested 2014 sp2 and it ready for packaging.

 

 

But i have made a clear argument to not packaging FME:

 

a simple script packaged run 30% slower on a 8core  16Gb system compared to a unpackaged on a singlecore 3Gb system.

 

Packaged is 30% slower on a singlecore system compared to unpackaged on this same ssingle coreystem.

 

 

 

So im waiting for it with great anticipation.

Reply