Skip to main content
Solved

Setting fme_db_operation value from an attribute


tim_wood
Contributor
Forum|alt.badge.img+8

I have an FGDB feature class which includes a "DBOperation" attribute with values of INSERT, UPDATE, or DELETE. I want to assign these to fme_db_operation but when I do this in an AttributeCreator, it gets changed to...

<at>Value<openparen>DBOperation<closeparen>

I've changed the AtrributeCreator to Conditional Value which seems to be happier.

Has anyone else had this experience?

Best answer by david_r

I can confirm using both FME 2016.1.3 and 2017 RC, looks like a bug. Consider reporting it to Safe.

If I use an AttributeRenamer rather than the AttributeCreator it works fine, though.

View original
Did this help you find an answer to your question?

4 replies

david_r
Evangelist
  • Best Answer
  • January 31, 2017

I can confirm using both FME 2016.1.3 and 2017 RC, looks like a bug. Consider reporting it to Safe.

If I use an AttributeRenamer rather than the AttributeCreator it works fine, though.


erik_jan
Contributor
Forum|alt.badge.img+17
  • Contributor
  • January 31, 2017

I agree with @david_r. You should report this to support@safe.com

In the meantime: have you tried using the AttributeValueMapper instead?


tim_wood
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • January 31, 2017
erik_jan wrote:

I agree with @david_r. You should report this to support@safe.com

In the meantime: have you tried using the AttributeValueMapper instead?

Thanks. Yes I thought of that. I wanted to see if it was worth pursuing the idea of storing the db operation as an attribute in an FGDB for later use when updating ArcSDE.

 

 


tim_wood
Contributor
Forum|alt.badge.img+8
  • Author
  • Contributor
  • January 31, 2017
david_r wrote:

I can confirm using both FME 2016.1.3 and 2017 RC, looks like a bug. Consider reporting it to Safe.

If I use an AttributeRenamer rather than the AttributeCreator it works fine, though.

Thanks, will do. AttributeRenamer is a good idea.

 

I've noticed when you create the fme_db_operation attribute, the value box changes to a drop down list of the allowed values. So there's obviously something special happening when setting that attribute.

 

 


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