Skip to main content
Solved

Feature Reader reading from wrong location - FME Server

P
Forum|alt.badge.img

I have a Feature Writer configured to write a csv to a parameterised path. In FME Server, this is configured as a Resource Path. This works OK and writes to: \\FMEServer\\resources\\data\\file.csv

A subsequent (text) Feature Reader uses the same parameterised path (with the filename). Unfortunately this appears to read from \\FMEServer\\repositories\\repository\\workspace/file.csv

Refer attached - have I configured this incorrectly or is this not supported?

This is for: FME Server 2016.1.0.1 - Build 1649

 

 

Best answer by david_r

You could try using a ParameterFetcher to extract the parameter value AssetWorkflowCSVPath into a feature attribute and use that in the FeatureWriter + FeatureReader instead of the parameter. At least then you'll be able to set breakpoints and inspect the contents.

View original
Did this help you find an answer to your question?

4 replies

david_r
Evangelist
  • david_rEvangelist
  • Best Answer
  • October 30, 2018

You could try using a ParameterFetcher to extract the parameter value AssetWorkflowCSVPath into a feature attribute and use that in the FeatureWriter + FeatureReader instead of the parameter. At least then you'll be able to set breakpoints and inspect the contents.

P
Forum|alt.badge.img
  • peterx
  • Author
  • November 1, 2018
david_r wrote:

You could try using a ParameterFetcher to extract the parameter value AssetWorkflowCSVPath into a feature attribute and use that in the FeatureWriter + FeatureReader instead of the parameter. At least then you'll be able to set breakpoints and inspect the contents.

That now works with a ParameterFetcher (I need two: one for Writer and one for Reader - as the Writer Summary wipes-out the attribute).

Seems like a bug if I don't use the ParameterFetcher.

H
Forum|alt.badge.img+2

Hi @peterx,

I haven't been able to reproduce this issue in either 2016.1 or 2018.1 so I think David's suggestion is the best option for you now.

 

If anyone else runs into this issue then please do let us know.
P
Forum|alt.badge.img
  • peterx
  • Author
  • November 1, 2018
hollyatsafe wrote:

Hi @peterx,

I haven't been able to reproduce this issue in either 2016.1 or 2018.1 so I think David's suggestion is the best option for you now.

 

If anyone else runs into this issue then please do let us know.

Thanks for looking. Yeah, it's a funny one - I don't think it's related to the internal/FME Shared Resource folder, but rather the Workspace Reader being tied to the repositories folder - when I cut-back to standard UNC path in the parameter, it still was looking at this folder, rather than the parameter.

Reply


Helpful Members This Week

Community Stats

30,960
Posts
117,340
Replies
38,748
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
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.