Skip to main content
  • EN

I can connect everything up but I get an error when I use either the Column Match or the Where clause options. I am not trying to update the geometry at all just hyperlinks to documents.

 

Thanks

 

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

FileGDB Writer: The `LMS_PERMITS_KEY' attribute could not be written. The containing feature has been dropped

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

Feature Type: `Lands/IPCoROW'

Attribute(encoded: UTF-8)  : `DOCLINK' has value `HTTPS://GISAPPS/GIS/LANDS_DOCS/TTLSE/51368,111-63345/120-V1-120-V1-587291 T3NR2W SEC 8.PDF'

Attribute(string)      : `Easement_Key' has value `45031'

Attribute(encoded: UTF-8)  : `HISTDOC1' has value `HTTPS://GISAPPS/GIS/LANDS_DOCS/EASEMENTS/111DISTRIBUTION/587291 T3NR2W SEC 8.PDF'

Attribute(string)      : `filegdb_type' has value `geodb_no_geom'

Attribute(string)      : `fme_db_operation' has value `UPDATE'

Attribute(string)      : `fme_feature_type' has value `EASEMENT.EASEMENT_DOCUMENT_PATH'

Attribute(string)      : `fme_geometry' has value `fme_undefined'

Attribute(entangled: string): `fme_type' has value `fme_no_geom'

     entangled to filegdb_type

Coordinate System: `'

Geometry Type: IFMENull

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

 

@donjensen​ It looks like you're working with Esri Parcel Fabric. FME supports reading parcel fabric, but not writing. So I'm not sure if we'll be able to get the updates working.

If you are able to attach a small'ish sample of the data as a File Geodatabase and your workspace, someone might be able to take a look and see if there is a way to do the updates. Also, might be good to know if this Parcel Fabric is created in ArcGIS Map or ArcGIS Pro - there are subtle differences in the new Geodatabases.

If you're data is also accessible through ArcGIS Portal, then it's possible you could use the Esri REST API and FME Feature Services writer to update your attachments.

I have checked with some of our database people and to their knowledge we are not using Parcel Fabric. The data that I am working with is simple polygon data. What is it that you saw that indicated we were working with Parcel Fabric?

 

Thanks

@donjensen​ Just from the feature extract you provided - looked like parcel data

We'd need to see the workspace, a little sample data and the target Geodb to try a reproduce this issue. Perhaps log a case with Safe Support (and reference this discussion) if you're not comfortable attaching data and workspaces here

Mark,

Here is some test data and my workspace that generates the error. I also included a log file from the run on my computer.

 

Thanks for the help

 

Don

@donjensen​ I think the issue is that some of your values for the join keys in the database are <null> and the combination of LMS_PERMITS_KEY and Easement_Key is not unique for some of the records.

imageIf you use two Updater transformers, one fot LMA_PERMITS_KEY and the other for the EASEMENT_KEY then I think you updates will work.

Thanks Mark. I feel sheepish right now. I should have known that the nulls would cause a problem. I set them all to zero and that took care of the problem. Thanks again.

Reply


Community Stats

30,418
Posts
115,549
Replies
38,226
Members
Terms & ConditionsCookie settings
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.