TerraFlex Desktop add-in v5.3

A new version of the TerraFlex Desktop add-in for ArcGIS Desktop (ArcMap) is available for download here (with required coordinate system files available here). The add-in supports TerraFlex on Connect and TerraFlex on InSphere workflows and replaces v5.0. Please see additional information below regarding new features, improvements, and bug fixes.

New Features & Improvements

1. Support for additional local coordinate systems in TerraFlex workflows: UK and the Netherlands. Users can now publish projects in local coordinate systems used in the UK and the Netherlands. This includes support for the transformations necessary when working with local correction sources. More information on supported coordinate systems can be found here.
   

   Region	Local Correction Datum	GIS Coordinate System
   UK	ETRF97 (frame of ETRS89)	Trimble: OSTN15 (OSGB36) Esri: British National Grid
   Netherlands	ETRF2000 (frame of ETRS89)	Trimble: RD 2018 (Amersfoort) Esri: RD New

2. Support for projected coordinate systems in TerraFlex workflows. Users can now publish projects in local, projected coordinate systems for supported regions. More information on supported coordinate systems can be found here.
3. Improvements to coordinate system nomenclature. In an effort to improve usability, the use of the term “coordinate system” has been standardized on. Specifically, the geodetic workflow option known as “Use a standard reference frame” is now known as simply “Best available” to better reflect the choice it provides. The user should refer to the “more details” link on the geodetics page of the Project Wizard for a full description of the options available.
4. Support for workspace archiving. The Project Wizard now provides a way to archive workspaces with the same outcome as if it were done through Map Viewer - to hide the project from field user devices. Forms can still be downloaded from archived workspaces.
5. Expanded set of geoids in TerraFlex on Connect workflows. In the initial release of local coordinate system support, the list of available geoids for TerraFlex on Connect workflows was limited to what’s also available through the Map Viewer. The list has now been expanded to include any standard geoid that Trimble provides and installs with the add-in.
6. Improvements to “add all” metadata link behavior. Previously, in order for the add-in to automatically select a feature class field for one of the metadata (or autofield) options, the name had to match the predefined name exactly, including case. This has been improved to be insensitive to case.
7. Changes in support for older versions of Esri software. Although this version still supports ArcGIS Desktop 10.2 (retired by Esri as of July 1, 2019) and 10.3 (retired by Esri as of December 1, 2020), older versions of Esri software may not provide full support for local coordinate system workflows in TerraFlex and thus the Classic/WGS84 geodetic workflow may be the only option provided.
8. Changes in Microsoft .NET Framework requirement. The add-in now requires Microsoft .NET Framework 4.7.2.

Bug Fixes

1. Projects could not be published to Connect in some localizations. Due to the string length of the translated Connect tag (“Created by TerraFlex ArcMap add-in”) used by the add-ins in some languages, publishing would fail. This has been fixed to trim the length of the string.
2. Migrated projects do not have the correct workflow settings after local migration. In some cases, migrated projects would display as using the “Advanced” workflow option (session-based, for post-processing) and if the user were to re-publish the project, this change would be propagated to the published workspace. This has been fixed and migrated projects will always use the “Basic” form-based download, real-time correction only workflow options. Projects that have already been migrated and may have the incorrect settings are also fixed in this version.
3. Migrated projects do not show as compatible with the current map document. In some cases, migrated projects would not be shown as compatible with the original map document. This has been addressed and projects should always be compatible with the original map document.
4. Uploaded features (for tasks) are duplicated in Connect when working with migrated projects. In previous versions, selected features uploaded to Connect as part of a task in a project (workspace) migrated from InSphere would not recognize previous uploads of the same features and duplicates would be created. This has been resolved.
5. Can’t initially Manage Tasks in a published project. In previous versions, the user would not be able to click on “Manage Tasks” in the dockable window if it was the first activity done while using ArcMap; the user would need to try downloading forms first and then would be able to enter the tasks area. This has been resolved.
6. Many incorrect WARN “Did not set metadata” logging statements for real-time corrected TerraFlex on Connect projects. If users were to look in the primary log file when working with real-time corrected TerraFlex on Connect projects, they would see a large number of WARN “Did not set metadata…” entries in the log. These statements are not relevant to this workflow and will no longer be logged.
7. Project Geodetics page of the Project Wizard did not display any information for projects when in read-only (view) mode. This page of the Project Wizard will now display the correct project geodetic information when the project is opened in either edit (compatible map document is open) or view (incompatible or no map document is open) modes. As a reminder, this page is always read-only for existing projects.
8. Problem with use of Microsoft SQL Server as the ODBC source for the office database. The recent office database schema upgrade did not work properly on Microsoft SQL Server and the database was left in a partially upgraded state. The underlying problem was fixed in this release.
9. Exception thrown when closing ArcMap when add-in extension component is disabled. In some cases, users will disable the extension portion of the add-in when they are not using it. This would sometimes cause an exception to be thrown when ArcMap was closed. This has been resolved.
10. Numerous “could not find layer” error messages in log files; occasional errors when storing features. Layers turned off in the map document (whether manually or by zoom scale) were not handled correctly by the add-in when opening the first project after loading. As a result, the add-in would not be able to find the feature class associated with the project layer in either the map document or the geodatabase workspace. This could result in errors at check-in or form download. This has been resolved.
11. Read-only feature class attributes used in editor tracking not handled properly. Attributes used by ArcMap’s editor tracking were not properly handled by the add-ins and resulted in errors storing null values in these read-only fields. This has been resolved and the add-ins will effectively ignore these fields.
12. Incorrect “Could not load *.ggf geoid file” popup message displayed. Although geoid file handling was changed in the previous release, some older, unused code was not completely removed and in some cases, users would receive a popup information message about the add-in not being able to load the selected geoid file.This would happen when the project was first loaded but actually the geoid was loaded properly and orthometric height calculations were done correctly. This has been resolved.
13. Error when creating a project in ArcMap 10.2.x. Due to a slight difference in linear unit settings in older ArcMap versions, projects could not be created under certain conditions. This has been resolved.

Advanced Configuration

In certain deployment scenarios, customers may need to manually configure the database connection. A configuration application can be downloaded here. Unzip the files and run it from there - no installation is required.