Skip to main content
  • EN

Hello community,

i am using an Feature Writer to write Feature classes in an Feature Dataset in an EGDB.

I found out that i need to enter the Feature Dataset Name/Feature Class Name hardcoded. For Example: FeatureDatasetName/FeatureClassName descriped in the following picture:

 

SDE Feature Writer with hardcoded (static) Feature Dataset and Featureclass Name


An dynamically generated Value like “@Value(FD_Name)/FCName” or even the whole value @Value(FD_name_and_FC_Name) is not working as Feature Class.

How i found that out? The Features get inserted in the Feature Class, even if i set Table Handling to drop and create. When i use the hardcoded (static) Feature Dataset and Featreclass Name the Table got dropped and created new, so it was working as expected.

SDE Feature Writer with dynamic/Attributvalue Feature Dataset and Feature class Name


When i use log level debug and use the dynamically (attribut value) Feature Dataset and Feature class Name, i get the following error Message which i dont get when i use the hardcoded (static) Feature Dataset and Featre class Name:

BADNEWS: File C:\Program Files\FME\metafile\MULTI_WRITER.fmf could not be opened
(D:\code\fme\source\engine\core\control\generiz.cpp:1630) class StatusInfo __cdecl STFGenericizer::processMetafile(const class stk::ex::UString<0> &,const class stk::ex::UStringArray<0> *,const class stk::ex::UString<0> &,const class stk::ex::UString<0> &,const class stk::ex::UString<0> &,const class stk::ex::UString<0> &,class STFAttributeName &,class STFMetaMapper &,class STFObjectNameConstraints &,bool &,bool &,bool &,class stk::ex::UStringArray<0> &,class stk::ex::UString<0> &,class std::vector<class STFFeatureType,class std::allocator<class STFFeatureType> > &,class stk::ex::UStringArray<0> &,class stk::ex::UStringArray<0> &,class stk::ex::UString<0> &,class std::vector<struct std::pair<class STFAttributeName,class stk::ex::UString<0> >,class std::allocator<struct std::pair<class STFAttributeName,class stk::ex::UString<0> > > > &,class stk::ex::UStringArray<0> &,class std::vector<class STFAttributeName,class std::allocator<class STFAttributeName> > &,class stk::ex::UStringArray<0> &,class stk::ex::UStringArray<0> &,bool &,bool &,class stk::ex::UString<0> &,class stk::ex::UStringArray<0> &,class STFObjectNameConstraints &,class stk::ex::UString<0> &,class stk::ex::UStringArray<0> &,class stk::ex::UStringArray<0> &,class stk::ex::UString<0> &)

I'm wondering whether this is expected behavior or a bug when using dynamic attribute values for the feature class name?

I am using FME(R) 2024.0.1.0 (20240328 - Build 24202 - WIN64).

Kind Regards,

Tim

In your concatenated FD_FC_name attribute, is there a forward slash in between? If I want the Feature type (Feature Class) name to be dynamic I would rather have the dataset and the feature class in separate attributes with a forward slash in between.

Lots of nuances on writing to a feature dataset. Are you creating new feature dataset (s) and new feature class (es) in your translation?

What is the Feature Dataset Handling parameter on your feature type? 

 

Here’s the doc to check out which parameter to use:

https://docs.safe.com/fme/html/FME-Form-Documentation/FME-ReadersWriters/geodatabase/feature_dataset.htm

Community Stats

31,923
Posts
121,242
Replies
39,545
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.