Skip to main content
Question

.Gdb and sde write problem


Forum|alt.badge.img+1

H? all,

I am trying to write my data over gdb and sde by processing. Some columns containing integers write null.

fme is working fine.

 

I'm not getting an error. but when I look at the database it looks null.

 

 

 

How can I solve this problem.

Thank You.

 

 

3 replies

erik_jan
Contributor
Forum|alt.badge.img+18
  • Contributor
  • April 2, 2020

Just guessing:

Could it be that both source features have the same attribute and it is empty in the Requester of the FeatureMerger and has a value in the Supplier of the FeatureMerger (and it will take the value from the Requester)?

Have you tried Redirect to Inspection application (In the Writers menu) to see if the attribute has a value when writing?


Forum|alt.badge.img+1
  • Author
  • April 2, 2020
erik_jan wrote:

Just guessing:

Could it be that both source features have the same attribute and it is empty in the Requester of the FeatureMerger and has a value in the Supplier of the FeatureMerger (and it will take the value from the Requester)?

Have you tried Redirect to Inspection application (In the Writers menu) to see if the attribute has a value when writing?

I tried Redirect to Inspection. fme is working fine. but he didn't take any action on the database.

 

I simplified the workbench. it's just reading and writing data. but the same error persists.

 

When I write as .shp, it does not have a problem.

 


nampreetatsafe
Safer
Forum|alt.badge.img+13
ssisman06 wrote:

I tried Redirect to Inspection. fme is working fine. but he didn't take any action on the database.

 

I simplified the workbench. it's just reading and writing data. but the same error persists.

 

When I write as .shp, it does not have a problem.

 

Are you able to share your workspace with us so that we can take a look at the feature type parameters, etc? If not, consider opening up a support case with us and share your workspace template (saving your cached features with your workspace) and we can try reproducing the issue locally.


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