Skip to main content
Solved

Feature Reader reading from wrong location - FME Server

  • October 30, 2018
  • 4 replies
  • 36 views
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.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

4 replies

david_r
Celebrity
  • david_rCelebrity
  • 8391 replies
  • 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
  • 49 replies
  • November 1, 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.

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
  • hollyatsafe
  • 719 replies
  • November 1, 2018

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
  • 49 replies
  • November 1, 2018

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.

Community Stats

32,061
Posts
121,725
Replies
39,688
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.