Package: assetic-esri
This package provides tools that can be used to assist with integration between Assetic and ESRI.  The tools may be included in the ArcMap python add-in, or in scripts run outside of the ArcMap desktop environmentChangelogRelease 1.3.0.2Added alternative method for getting layer fields to support enterprise geodatabase layer connectionsRelease 1.3.0.1Added boolean parameter for creation of Functional Location when checking for it’s existence during asset associationRelease 1.3.0.0Added support for Component and Dimension ‘upsert’ where the Component and or Dimension is created as
part of the Asset update if the Component/Dimension does not already exist.
Requires Assetic SDK 2023.16.1.2 minimum, and configuration setting to enableRelease 1.2.1.1Resolve release issueRelease 1.2.1.0Fixed an issue when creating assets where domain lookups for Subtype Field were not resolved, resulting in the create applying the “CodedValue” for domain attributesRelease 1.2.0.10Fixed an issue when writing the asset Id value back to the layer attributes when using a “CodedValue” domain and resolving lookupsFixed an issue when updating assets where domain lookups were not resolved, resulting in the update applying the “CodedValue” for domain attributesFixed an issue where the component type was set to an incorrect value if the type was defined by an attribute field, rather than a defaultRelease 1.2.0.9Support subtypes where the domain is of type “CodedValue” and the description value is needed rather than
the code value which is the default.
To use set <resolve_lookups>True</resolve_lookups> in config for the layerCater for data with M dimension (strip null M from upload to Assetic)Release 1.2.0.8Standardise functional location creationRelease 1.2.0.7Correct error with support for table only layersRelease 1.2.0.6Improve unhandled exception logging by ensuring exception still output to stderr as well as loggerSupport legacy use of deprecated CommonTools.force_use_arcpy_addmessageImprove messaging around testing of Functional Location existence prior to creationRelease 1.2.0.5Moved create/update methods from python-sdk in to this packageRelease 1.2.0.4Fixed logging issuesMoved bulk_update_spatial method from python-sdk to assetic-esri-sdkRelease 1.2.0.3Moved common GIS functionality to shared Assetic Python SDK (pypi: assetic)Release 1.2.0.2Fix issue where functional location not created if type defined by
an attribute field rather than a defaultRelease 1.2.0.1Fix issue where spatial upload was skipped in some circumstancesRelease 1.2.0.0Introduced support for layers with no spatial data, i.e. tablesAllow for updating components of the same type by including
component name when obtaining the component to updateEnsure log level is correctly setRelease 1.1.3.2Improve messaging if missing configurationRelease 1.1.3.1Cater for partial asset creation whereby the asset is created
but a component, dimension, or functional location association
fails.  Reported as a partial success, and the GIS is updated
with the asset Id and optionally the component ID if createdRequires the assetic python package 2020.6.1.1 as a minimumRelease 1.1.2.1Support configuration where id not a functional location fieldImprove messaging around missing configurationsRelease 1.1.2.0Add option to apply custom calculation script that allows
fields from layer to be used to derive new fields to be used for
input to Assetic.  The derived field does not need to be in the layerRelease 1.1.1.1Add XML configuration option to set threshold at which bulk
update occurs via Data Exchange rather than per assetRelease 1.1.1.0Introduced support for creating and updating Functional Location for a Functional Location layerIntroduced support for associating an asset with a Functional Location on asset creation or updateIntroduced bulk update process where feature count exceeds 250.
Data Exchange is used to apply the updates as it is a more
efficient process for large volume updates.Release 1.0.1.14Fix issue caused by missing bracket in version checkRelease 1.0.1.13Check the Assetic folder exists in %APPDATA% and if not create itFix issue reading XML configuration setting for upload_spatialRelease 1.0.1.12When initiating the settings in the xml configuration file will be
used in preference to the passed in logfile name and levelPrior to initialisation of the logging, unhandled errors will be
written to %APPDATA%/assetic/addin.logRelease 1.0.1.10Cater for multiple network measure addition records against a
single component provided the shape differs for eachRelease 1.0.1.9Cater for arcs/circles in polygon and polyline definitionsAdd arcpy Progressor option for progress messages when using
model builderRelease 1.0.1.8On asset creation the status did not match the layer configurationRelease 1.0.1.7Add support for creating and updating Component, Dimension and Address, standardise spatial upload.Improve error logging to catch unhandled exceptionsMinimum required Assetic package is 2019.2.3.0Release 1.0.1.6Correct potential issue with unsupported spatial data uploadRelease 1.0.1.5Add property config.force_use_arcpy_addmessage as boolean.
If using Model Builder in ArcMap it ensures messages are written to the Model Builder run dialog rather than a separate
pop-up dialog that can get lost behind the Model Builder dialog.  Default = FalseRelease 1.0.1.4Allow a filter to be provided on asset creationCorrect issue with setting log fileRelease 1.0.1.1Publish to pypiRelease 1.0.1.0Include default field configuration optionRelease 1.0.0.0Initial Build