Skip to main content
  • EN

I am using a FeatureReader to read a Postgres db table. As I want the workspace to be easily migrated from developement to production system, I use Published Parameters to supply the connection parameters, meaning I use a parameter committing the name of a FME-DB-Connection and two parameters (Published_Parameter_Schema.Published_Parameter_Table) for the Feature Types to Read. Unfortunately, no output is generated from the generic port (no error message in the transition log), even if I expose the attribute within the FeatureReader or with an AttributeExposer afterwards.

As a workaround, I use a AttributeCreator to commit the Published Parameters for the schema and the table into attributes before using them as input for the FeatureReader. With exposing the attributes from the Postgres-DB inside the Transformer, this works fine.

But I keep wondering, why it doesn't work using Published Parameters directly?

 

What version FME do you use? This works perfectly fine in 2019.1 and 2020.2.

Do you have uppercases in you schema and/or table name? Because those are case sensitive.

Update 21.01.2021:

I upgraded my FME Version to 2020.2, but the problem still exists.

I checked the casing and also tried to change the Published Parameters into lowercase, similar to the attributes I use as a workaround.

Did you also trie to connect to a Postgres/PostGIS-Database?

**********************************************************

I use FME 2020.1. So I will upgrade my FME version and see, if that was the problem. Thank you!

Reply


Community Stats

30,418
Posts
115,549
Replies
38,226
Members
Terms & ConditionsCookie 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.