Skip to main content
Solved

Setting fme_db_operation value from an attribute

  • January 31, 2017
  • 4 replies
  • 122 views
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.

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.

4 replies

david_r
Celebrity
  • david_rCelebrity
  • 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+23
  • erik_janContributor
  • 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
  • tim_woodContributor
  • Author
  • 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?

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
  • tim_woodContributor
  • Author
  • Contributor
  • 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.

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.

 

 

Community Stats

32,154
Posts
122,047
Replies
39,812
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.