Hi @jamesleversha,

It depends on what your trying to read as the schema. I suspect you are not getting your schema form schema feature attributes. If that's the case I would edit "schema sources" and remove "schema from schema feature" so you just include the readers schema (SDE30).

This is a great tutorial series on dynamic workspaces. In particular if your looking for working with schema features then the "Dynamic Workflows: Destination Schema is Derived from a Schema Feature" will be useful.

https://knowledge.safe.com/articles/1050/dynamic-workflow-tutorial-introduction.html

Richard

---

Hi @jamesleversha,

It depends on what your trying to read as the schema. I suspect you are not getting your schema form schema feature attributes. If that's the case I would edit "schema sources" and remove "schema from schema feature" so you just include the readers schema (SDE30).

This is a great tutorial series on dynamic workspaces. In particular if your looking for working with schema features then the "Dynamic Workflows: Destination Schema is Derived from a Schema Feature" will be useful.

https://knowledge.safe.com/articles/1050/dynamic-workflow-tutorial-introduction.html

Richard

Thanks Richard,

 

 

I will check this out when im back at work on Monday. I have already tried unchecking that schema from feature option.

 

 

I dont think it will ever find a schema that is named 'STATEWIDE_V_PROPERTY_MP_ADDRESS' because that is the name I want the table to be called and I have manually assigned that. The schema I am looking for is VMPROP.V_PROPERTY_MP_ADDRESS, which should come from the schema definition name: fme_feature_type shouldn't it?

 

 

Essentially, I dont understand why its looking for my table name in the schemas and not looking for the fme_feature_type attribute in the schemas.

 

 

And why does it work for the MapInfo standard writer with STATEWIDE_@Value(fme_feature_type) as the table name with all the same options checked?

 

 

Cheers,

 

 

James

 

---

@RichardAtSafe,

So i have tested this, and just wondering on the the exact same reader....

This works

But this doesn't

Cannot find a matching schema named 'STATEWIDE_V_PROPERTY_MP_ADDRESS' in the known set of schemas: 'VMPROP.V_PROPERTY_MP_ADDRESS, VMADMIN.LGA_POLYGON'. Known schema sources are: 'SDE30_2, SDE30_1'. Please verify writer feature type configuration.

I have figured this workaround, and it works. or is this the way it should be done in the fetaure writers when joining a string to a parameter?

@Evaluate(STATEWIDE_)$(TABLE_NAME)

Cheers,

James

---

Hi @jamesleversha, a possible reason for the error is that the value of "fme_feature_type" has been changed at some point in the workflow. Check also this point.

---