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_54b454c0f7fb4cc2ac2b5c900a7c6b8153 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
Did you try running Update Data Loading Workspace Schema to updates its schema to match the asset package?
I created a new workspace with the new asset package so this tool didn't change anything.
I have reduced my migration workspace to just a single structure feature class. I have also removed the 'network attributes' for installdate, retiredate, availablecapacity from the asset package. I have populating in the feature class mapping workbook only required fields. After reducing populating attributes and network attributes that possibly the tool is looking for, I am still getting the same error, that a field could not be found or retrieved properly. I have attached the feature class data mapping. What else could the Load Workspace tool be looking for? @MikeMillerGIS
@MikeMillerGIS @RobertKrisher I have stripped down the asset package so I am only dealing with ootb attributes. I ensure assetstate is populated, which seems to be the only non-nullable field I can manipulate. I don't see which other fields the tool could be looking for, for the more simple, StructureJunction. I also don't understand why the messages states rows with errors were exported to a scratch space AND appended to StructureJunction (they were not). Previous runs/builds only report appended if there are no errors. Please let me know if you have a next step as I am running out of things to try and trying to determine if this is a bug. I have tried both ArcGIS Pro 3.6.2 and 3.6.4.
@strmside please log an issue as this may be specific to the data/configuration you have in your asset package. Mike is out of office right now, but my guess is that having sample data will help.
I have some concerns about the data model I see in this spreadsheet (no field reuse, haven't paired back expanded model, etc) but I'm going to hope that's because you've had to regenerate your mapping sheets. Remember, if you implement the expanded model you need to make sure you remove anything you don't need (fields, asset types, etc) otherwise you will end up with a large, less performant model. If you plan on just adding your existing data model onto a foundation, start with the essentials model then just make sure that you're reusing fields (achorsize, structuresize, etc).
Could you share a zip with inputs/outputs and gp call so I can try to repo? Sorry for my delayed response, I was out on vacation.
If you renamed or removed any fields present in attribute rules, you may want to look at those.
Thank you, but I have not added any attribute rules (or contingent values) to the electric expanded asset package.