Skip to main content
Question

Passing multiple input values to Private parameter

fmeuser_gc
Contributor
Forum|alt.badge.img+8

In my workspace, I've three ESRI GeoDB reader Feature Types with WHERE condition. Here values in the WHERE condition are passed from a private/published parameter input values.

Few things to be considered -

  • There are approximately around 100 values to be passed in sequential order from Excel sheet to Parameter values.
  • Workspace has to run completely for every input parameter value

 

Currently I was passing each value manually to the parameter and is time consuming.

Any thoughts on doing this more efficiently and quickly?

 

Thanks in advance!

Yash K

    3 replies

    takashi
    Influencer
    • takashiInfluencer
    • May 19, 2020

    Hi @fmeuser_gc, sounds that the FeatureReader could be a quick solution.

    Read the parameters from the Excel dataset one by one, build WHERE parameter value, and pass it to the WHERE parameter in the FeatureReaer configured with Esri GDB.

    fmeuser_gc
    Contributor
    Forum|alt.badge.img+8
    • fmeuser_gcContributor
    • Author
    • Contributor
    • May 20, 2020
    takashi wrote:

    Hi @fmeuser_gc, sounds that the FeatureReader could be a quick solution.

    Read the parameters from the Excel dataset one by one, build WHERE parameter value, and pass it to the WHERE parameter in the FeatureReaer configured with Esri GDB.

    Thanks @takashi. But is it possible to have multiple feature types in FeatureReader with different WHERE condition for each of the FeatureType?

    I've tried this FME 2019, but looks like not supported. Is this supported in FME 2020 ?

    Yash K
    takashi
    Influencer
    • takashiInfluencer
    • May 21, 2020
    takashi wrote:

    Hi @fmeuser_gc, sounds that the FeatureReader could be a quick solution.

    Read the parameters from the Excel dataset one by one, build WHERE parameter value, and pass it to the WHERE parameter in the FeatureReaer configured with Esri GDB.

    No it's not possible, but it's OK if you pass pairs of feature type name and corresponding WHERE clause to the FeatureReader one by one.

    Reply


    Helpful Members This Week

    Community Stats

    31,370
    Posts
    118,974
    Replies
    39,000
    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.