Skip to main content
Solved

data download service input schemas not matching output schemas

  • May 4, 2017
  • 5 replies
  • 17 views

Forum|alt.badge.img

Hi,

I'm wondering how to modify this so that output schemas match those input?

Regards,

Richard

Best answer by takashi

Hi @richardtriesfme, the FeatureReader outputs first a schema feature for each feature type via the <Schema> port and a Dynamic writer feature type can refer the schema feature as its schema source. Try this.

  1. Connect the <Schema> port of the FeatureReader and the writer feature type directly.
  2. In the writer feature type, check the Dynamic Properties checkbox and select "Schema From Schema Feature" as the Schema Source.
  3. If you have set fme_feature_type to the Feature Type Name in the writer feature type, you can leave the Schema Definition Name parameter the default ("Default from Feature Type name above"), like this screenshot. Otherwise, set fme_feature_type to the Schema Definition Name explicitly.

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.

5 replies

takashi
Celebrity
  • Best Answer
  • May 4, 2017

Hi @richardtriesfme, the FeatureReader outputs first a schema feature for each feature type via the <Schema> port and a Dynamic writer feature type can refer the schema feature as its schema source. Try this.

  1. Connect the <Schema> port of the FeatureReader and the writer feature type directly.
  2. In the writer feature type, check the Dynamic Properties checkbox and select "Schema From Schema Feature" as the Schema Source.
  3. If you have set fme_feature_type to the Feature Type Name in the writer feature type, you can leave the Schema Definition Name parameter the default ("Default from Feature Type name above"), like this screenshot. Otherwise, set fme_feature_type to the Schema Definition Name explicitly.


Forum|alt.badge.img

Thanks Takashi,

I believe I have done this now however I am still getting extra attributes in the output that do not exist in the source.cadextractorworking.fmw

Regards,

Richard


takashi
Celebrity
  • May 4, 2017

Thanks Takashi,

I believe I have done this now however I am still getting extra attributes in the output that do not exist in the source.cadextractorworking.fmw

Regards,

Richard

I think the dynamic properties setting in your workspace should work as expected. How did you confirm that the extra attributes don't exist in the source feature type?

 

 


takashi
Celebrity
  • May 4, 2017

Thanks Takashi,

I believe I have done this now however I am still getting extra attributes in the output that do not exist in the source.cadextractorworking.fmw

Regards,

Richard

Ah, I didn't check the User Attributes tab in your writer feature type. In a dynamic writer feature type, it's not necessary to define any user attribute unless you want to define specific additional attributes. Remove every attribute definition here.

 


Forum|alt.badge.img
Ah, I didn't check the User Attributes tab in your writer feature type. In a dynamic writer feature type, it's not necessary to define any user attribute unless you want to define specific additional attributes. Remove every attribute definition here.

 

Thanks Takashi,

 

 

This has resolved it.

 

 

Regards,

 

Richard