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

[strmside]

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

[MikeMillerGIS]

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.

[streamside]

I have created a new workspace and tried the workspace loading with 3.7.  While It did get past the errors noted in the original post it has a new error "Error 000358: Invalid Expression".  When I reviewed the logs and assume the row it was looking at based on which it had just appended, this row in the DataReference workbook has a blank field/no query i.e., all data should be copied from said feature class.  The logs showed all ConductorInfo rows successfully appended, therefore the assumption is the failure at ConduitInfo (shown in screen shot).

[MikeMillerGIS]

There was a change on an underlying library, which causes empty expressions to fail.  You will need to add an expression like 1=1 for now.  We are planning to get a fix into a 3.7 patch.

[streamside]

Ok, I can confirm this change works and I need the first patch for 3.7 in order to use python to run a full build (multiple gp tools), since a manual change/edit of the DataReference workbook is still required.

[TSmith]

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

[strmside]

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