Select to view content in your preferred language

Cannot identify field that is missing - ERROR 160144: An expected Field was not found or could not be retrieved properly.

774
12
3 weeks ago
strmside
Occasional Contributor

I had previously built a un with version 3.1 of the expanded electric asset package using simple data mapping, create workspace and load workspace - I had a well working script.  I am attempting to update the asset package to the latest version where field changes were made to life cycle status and asset state was added, for example.  In Load Workspace I get this error for every feature class until it fails: ERROR 160144: An expected Field was not found or could not be retrieved properly.

I have reviewed the mapping, the Data Reference and ensured all required fields are being populated.  In the first log of this error, there are no issues in the workspace workbook for mapping.  I.e., it tries to load a simple aerial marker but that mapping workbook has no errors or warnings.  By the time the tool actually fails it is landing on an electric line or electric device.  Each time, despite this error the logs say the data is appending yet fails.  I am looking for suggestions to identify missing field or some other bug?

Processing C:\LocalArcGISWork\elec_fac_data_for_sql_v2.gdb\ElectricFacilityData\AerialMarker -> C:\LocalArcGISWork\migration_workspace_v50\ElectricExpanded_AssetPackage.gdb\StructureJunction
WARNING 000594: Input feature 1: An expected Field was not found or could not be retrieved properly..
WARNING 000594: Input feature 2: An expected Field was not found or could not be retrieved properly..
WARNING 000594: Input feature 3: An expected Field was not found or could not be retrieved properly..
WARNING 000594: Input feature 4: An expected Field was not found or could not be retrieved properly..
WARNING 000594: Input feature 5: An expected Field was not found or could not be retrieved properly..
WARNING 000594: Input feature 6: An expected Field was not found or could not be retrieved properly..
WARNING 000594: Input feature 7: An expected Field was not found or could not be retrieved properly..
WARNING 000594: Input feature 8: An expected Field was not found or could not be retrieved properly..
WARNING 000594: Input feature 9: An expected Field was not found or could not be retrieved properly..
WARNING 000594: Input feature 10: An expected Field was not found or could not be retrieved properly..
WARNING 003819: Exported 53 rows that were skipped to \\ceanet1\profiles$\ashleys\Documents\ArcGIS\Projects\MyProject_new_351\scratch.gdb\fc_54b454c0f7fb4cc2ac2b5c900a7c6b81
53 row(s) from C:\LocalArcGISWork\elec_fac_data_for_sql_v2.gdb\ElectricFacilityData\AerialMarker were appended to C:\LocalArcGISWork\migration_workspace_v50\ElectricExpanded_AssetPackage.gdb\StructureJunction

 

0 Kudos
12 Replies
MikeMillerGIS
Esri Frequent Contributor

Ok, we did not track down exactly when that change to append occurred, but it was in 3.6.  We did not make the changes in Data Loading at 3.6 to auto turn off Preserve, but we did in 3.7.  Glad support figured it out.  You should be fine just setting to to False.

0 Kudos
TSmith
by
Regular Contributor

If you renamed or removed any fields present in attribute rules, you may want to look at those.

0 Kudos
strmside
Occasional Contributor

Thank you, but I have not added any attribute rules (or contingent values) to the electric expanded asset package.

0 Kudos