Skip to main content

2024.2 (24820)

 

I am building a self serve workspace app for flow. the user will drag and drop a dwg onto the app.

The workspace will convert the mapped drive to UNC and use that for a featurereader.

prior to the featurereader the path will go through the filenamepartextractor. The output is NOT exactly the same location as input, and changes certain parts depending on the file dragged and dropped by the user. 

I use the source name in the filenamepartextractor and then build the output folder (which may or may not exist in full or in part). Then there are 3 types of files to output to that folder.

I currently have the output dwg name built by hardwiring the filename and extension. 

The form workbench runs successfully with no output in the destdataset which is set as the output attribute for the filename. there is however a file in the workspace folder named @Value(DestDataset) with no extension. Tested by renaming this file and adding dwg extension (which opened correctly in autocad). Why does the attribute value not get used for the output? It does the same when run in flow. It is creating all 3 outputs in the folder where the fmw resides. but not getting the attribute value.

I am not able to set a specific flow resource folder for this output.(AS the input/output changes each time)

 

Form Log
​​​​​​
Flow Log
attribute manager setting the new path and filename and extension
​​​​​​
writer 1 output value
​​​​​​

 

Anything in the log? What version fme?

I replaced all writers with featurewriters. that is all it required. I think it is being looked at internally.

 

 

I dont see any quote marks.

and the path building looks to be correct. this is the output directly in front of the writer.

I have the extension on the user parameter here but have also used it on the writer destination as well.

My feeling is that somewhere quotes are introduced, making FME using the variable as a string. But without the workspace this is hard to pinpoint. Can you check / printscreen the values of DestDataset just before it arrives at the writer?

Are the attributes from the initiator being correctly passed the the output features? 

 

Does the output path look correct in the inspector before the output?

Community Stats

32,026
Posts
121,628
Replies
39,647
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.