Skip to main content
Question

issue - Arcsde Writer (Row Match)

  • October 29, 2024
  • 7 replies
  • 115 views

jokerfme
Contributor
Forum|alt.badge.img+1

Hello ,

I need a help 

I successfully updated a point geometry in the ArcSDE writer within a specific version.

 

I encountered an issue.

When I select "Update Mode" and set "Row selection - Columns " to ObjectID, I get an error translation  running  . But if I leave "Row seletion - Columns" empty, the translation runs successfully.

 

The "Row selection - Columns " field turns red when left empty, and I’m unable to click "OK." To work around this, I temporarily set "Row Selection - Columns" to ObjectID, click "OK," and then use a Remover transformer before the writer to remove ObjectID—and when I run the workspace ,it  works great and translation is successfully .

 

But ’m unclear on how FME identifies the correct point to modify it ,how to resolve my issue ?

 

Update Spatial columns : Should be yes or no ?

FME version: 2021, 64-bit.

Thanks in advance

7 replies

jokerfme
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • October 30, 2024

Transaltion successful when I remove all attributes before writer ,even writer has red field 

 

but if I let objectid or other unique id , I got error running translation .

how to fix it ?

 

 


AliAtSafe
Safer
Forum|alt.badge.img+22
  • Safer
  • October 30, 2024

Hi, @jokerfme.

Thanks for posting your question.

Reading your question here, we have a few suggestions.

  1. If you are wanting to update the geometry, the Update Spatial Columns should be set to Yes
  2. If the Match Columns parameter is the issue, a quick solution could be to try using the WHERE clause option. You could use the ObjectID there ("ObjectID" = @Value(OBJECTID))
  3. If you want to stick with just the Match Columns parameter, ensure the case matches.

If these don’t work out, we would like to request your workspace. It’ll assist problem solving the issue. Hope this helps!

Thanks!


jokerfme
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • October 30, 2024

@AliAtSafe 

Thank you for your suggestions 

I've spent the whole day working to resolve my issue. Here’s what I’ve found so far:

When I run my workspace after using row selection with the "match column" set to ObjectID or applying a WHERE clause, I receive a warning indicating that ObjectID and GlobalID are not editable.

After a few minutes, the translation completes successfully, but then an error appears translarion error running . However, when I check the results in ArcMap, I see that the changes have already been applied in the version.

 

I’m still not entirely sure why this is happening.
Do you have any other suggestions that could help resolve this issue?

 I am testing only with one record . 

Fme version 2021 

 


AliAtSafe
Safer
Forum|alt.badge.img+22
  • Safer
  • October 31, 2024

Hello, @jokerfme,

Thanks for trying that out and providing details. Interesting; to confirm, it does work but throws an error? Could you provide the error that is being thrown before it writes successfully? If you can, could you share your workspace and log file? It’ll help troubleshoot this issue better.

Thanks!


jokerfme
Contributor
Forum|alt.badge.img+1
  • Author
  • Contributor
  • November 5, 2024

Hello @AliAtSafe 

Uploading the workspace is challenging due to data security restrictions, as it’s not permitted.
 

I have tested inserting and updating with just one point. This is the log file, showing that I tried also where clause approaches, but encountered an error when running the translation.

However ,I can see the result of changes in Arcmap .

 

As the admin, I have full permissions, and I verified in the database that insert, update, and delete actions are permitted. However, I'm wondering because I can delete any point by matching the ObjectID column, and the translation completes successfully.

 

But when I attempt an insert or update, the following log file appears:

 

Feature Caching is ON

Fast deletes enabled

The 'HAS_Z_VALUES' keyword is set to 'AUTO_DETECT'. With the exception of MultiPatch feature classes, the dimensionality of new feature classes will be based on the first feature written to the feature class. (Features with no geometry are considered 2D)

A default z-value of '0' will be used for all 3D features where z-values are not provided

Esri Geodatabase Writer: Not simplifying geometries being written

Esri Geodatabase Writer: The field 'OBJECTID' in feature type 'Featureclass name' will not be updated since it is not editable

Esri Geodatabase Writer: The field 'GLOBALID' in feature type 'Featureclass name' will not be updated since it is not editable

Starting an edit session

Geodatabase Writer: WHERE clause is evaluated as '("OBJECTID" =162823)'

Destination Feature Type Routing Correlator (RoutingFactory): Tested 1 input feature(s), wrote 1 output feature(s): 0 matched merge filters, 1 were routed to output, 0 could not be routed.

Final Output Nuker (TeeFactory): Cloned 0 input feature(s) into 0 output feature(s)

GeodatabaseRelationshipFeaturesPipeline::GeodatabaseRelationshipFeatures (SortFactory): Finished sorting a total of 0 features.

All edits made during the edit session were saved

Closing the Esri Geodatabase writer

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Feature output statistics for `GEODATABASE_SDE' writer using keyword `GEODATABASE_SDE_3':

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

                               Features Written

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Featureclass name                                                              1

==============================================================================

Total Features Written                                                       1

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

                            Features Read Summary

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

==============================================================================

Total Features Read                                                          0

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

                           Features Written Summary

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

Featureclass name                                                              1

==============================================================================

Total Features Written                                                       1

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-

-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

-~                                                                             ~-

-~    Feature caches have been recorded at every stage of the translation.     ~-

-~                      To inspect the recorded features,                      ~-

-~              click the feature cache icons next to the ports.               ~-

-~                                                                             ~-

-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-

Translation was SUCCESSFUL with 7 warning(s) (1 feature(s) output)

FME Session Duration: 45.2 seconds. (CPU: 16.1s user, 4.6s system)

END - ProcessID: 20044, peak process memory usage: 707924 kB, current process memory usage: 252120 kB

Translation was SUCCESSFUL

Error running translation

 


AliAtSafe
Safer
Forum|alt.badge.img+22
  • Safer
  • November 28, 2024

Hi, ​@jokerfme.

I’m very sorry for not reaching out sooner. Thank you for your great patience. Let me know if you’ve found a workaround or created another community post. Thank you for providing those extra details. All good if you can’t provide your workspace. Would like to ask the build number of FME Desktop 2021? So we can test it on that build to see if this is an occurring issue. Thank you once again!


bwn
Evangelist
Forum|alt.badge.img+26
  • Evangelist
  • November 28, 2024

At least in FME2021, there is a bug with some Writers that it will show the “Match Column” Parameter setting in “Red”  if the specified Attribute is not listed in the “User Attributes” Tab.  Some Writers don’t even give you the ability to select it from an Attribute Drop Down if it is not in the “User Attributes” Tab.

This is common with say, OBJECTID, where it is an Attribute you do not wish to Write, but only use as Match/Lookup field.

My workaround on FME2021 is to generally initially leave OBJECTID in the User Attributes Tab,  then go back and set the Match Column parameter, then go back into User Attributes Tab and remove OBJECTID.  The Parameter may graphically show as “Red” in the Dialog but it is still a valid parameter setting and the Writer will Write.

Getting warnings on “OBJECTID” not being updateable on write is normal behaviour on an SDE / ArcGIS format write.


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