I have tried to write back to a test geodatabase and everything worked fine the test geodatabase was pretty basic with one feature class with no coded values, but when given a larger geodatabase this is the error I run into. any help would be great.
I have to admit we're not doing a great job providing comprehensible error messages in the GIS Module today, so there could be many possible reasons this message pops up. Would you share your GDB with us so we can take a closer look?
To Add to Rui's comments
The Geodatabase API used by TBC, supports only simple feature classes/ geodatabases.
This means advanced functionality like geometric networks, attachments, relationship classes, sub types, Editor tracking etc are not supported and can potentially cause problems like this, when writing back to the *.gdb
As a result we recommend customers only use simplified geodatabases when working with TBC.
Many customers use a 'staging' geodatabase to get round this problem
i.e. make a copy of the original geodatabase without any of the advanced features to be used with TBC. Once the updates have been committed from TBC back to this *.gdb you can use the various ESRI GP tools to load this data back into the original geodatabase with 'advanced' configuration.
I have seen such issues with feature classes having global ID fields also.
I too concur with the above statements regarding issues connecting feature classes having Global ID's, editor tracking, etc, with SDE datasets to the TBC GIS module, as I have been experiencing this for quite some time. The only successful workaround is like Mr. Harrison stated, making a 'staging/skeletonized/dummy' version of the feature class and processing from that simplified format. There still seems to be other lingering issues such as field matching, data formatting, default values, etc. when attempting variations of this workflow. However, Trimble needs a big KUDOS for the effort made so far, as the (advanced) schema/fxl we operate with is the foundation for everything we do with survey grade GIS solutions. I am looking forward to the next release, and hopefully any ongoing improvements to this module.
Thank you for your support! Please keep sending us suggestions and requests because we do want to make the GIS Module (much) better and it would be great to hear from users like you to help us plot the roadmap.
Retrieving data ...