Skip to main content
Question

Dynamic Writer Map Info Extended


Forum|alt.badge.img

Hey I might be missing something here...

I cant get the dynamic schema to work on the Map Info Extended Writer.

When i try to load this in it says that its cant find the schema and features cant be written...

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

Shouldnt the matching schema be named to the fme_feature_type not the table name? or does something happen when using a parameter in the table name.

The dynamic schema appears to work if i change the value of the table name to "STATEWIDE_@Value(fme_feature_type)" which seems weird.

I also cant uncheck the fanout dataset option. It unchecks then i click ok, then i go back in and its checked again.

Cheers,

 

James

4 replies

richardatsafe
Safer
Forum|alt.badge.img+10

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


Forum|alt.badge.img
richardatsafe wrote:

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

 


Forum|alt.badge.img

@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


takashi
Evangelist
  • May 27, 2018

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.


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