The following information applies to ArcFM Solution applications that run on ArcMap. This includes ArcFM, Designer, ArcFM Viewer, Conduit Manager, Network Adapter, and Fiber Manager.
This page describes the functionality added to the current release for all products in the ArcFM Solution suite.
This section provides a list of API changes for 10.0.1. Be sure to review the API changes and perform any migration steps for releases between your original version and the one to which you are upgrading.
- New ArcFM Geodatabase: If you're configuring a geodatabase to use the ArcFM Solution for the first time, follow the steps on the Configure New Geodatabase page.
- ArcGIS/ArcSDE Note: A mixed version environment is not supported. If you are upgrading to ArcGIS 9.3, you MUST upgrade your geodatabase to ArcSDE 9.3 as well. ArcFM Errors will occur if an ArcGIS 9.3 machine attempts to access an ArcSDE 9.2 machine or an ArcGIS 9.2 machine attempts to access an ArcSDE 9.3 geodatabase.
- Licensing Note: If you're upgrading from a release prior to 9.2, you will need to obtain new licenses for the 9.3 release. Request a new license at the Telvent Technical Support web page. Contact Telvent with licensing questions.
- License Manager: The version of License Manager MUST match the version of all ArcFM Solution products installed.
- Context-Sensitive Help: Context-sensitive help (What's This tool) does not work properly with Windows 7 and Windows Server 2008 R2. To resolve this issue, download from Microsoft the WinHlp32.exe file for your operating system and execute it.
- Beware of WordPad: When editing configuration files, DO NOT use WordPad. It has been known to insert characters that can cause malformed XML.
ArcFM Solution 10.0.1 and 10.0.1 SP1 require ArcGIS Desktop 10 with Service Pack 1. ArcFM Solution 10.0.2 requires ArcGIS Desktop 10 with Service Pack 2. In addition, the following tasks are required to run ArcFM Solution 10.0.1 and later:
- ArcGIS Desktop 10.0 SP1
- ArcGIS Desktop VBA Resources for Developers
- VBA license from Esri
VBA Resources Installation
ArcFM Desktop 10.0.1 and later applications require Esri's ArcGIS Desktop VBA Resources for Developers. As of ArcGIS Desktop 10.0, Esri does not install VBA by default as it had in former releases. The requirement to install VBA will be removed permanently in future releases of ArcFM, coinciding with Esri's removal of VBA from distribution.
To obtain a free VBA 10 authorization file (license), contact Esri customer support. More details on ArcGIS Desktop and VBA can be found here.
ArcFM Desktop - Recommended Patches
Applies to: Desktop users only.
Esri service packs and patches can be located here. Depending on the functionality you use in ArcFM Desktop, there may be a few that should be applied. The Sketch Tool patch is strongly recommended for those editing users who use the Attribute Editor.
Patch: Sketch Tool (recommended)
Problem: After placing a feature in ArcMap 10.0 SP1, the cursor reverts from the cross-hairs to the standard cursor, leading the user to believe he must select the feature in the Features tab again to place another.
Solution: With this patch applied (download patch here), the cursor will not revert to the standard cursor after placing a feature and editing behavior will remain consistent with earlier releases.
Patch: Split Tool (recommended)
If your complex edges have ESRI relationships with message notification turned on you will benefit from this patch. Also, if you use Feature Linked Annotation, you will benefit from this patch.
Problem: Depending on your data definition, you may see the one of the following errors when splitting complex edges.
After the user clicks OK, ArcMap rolls the feature back to its state prior to the split. There are a few work-arounds to this functionality, but the work-around depends on the data conditions and your editing environment. For more information, contact Telvent Technical Support.
Solution: To acquire a permanent fix regardless of data conditions or environment, download the ArcGIS 10 SP1 (Desktop) Split Custom Features with Relationship Propagation patch from Esri. It is available here.
Applies to: All Desktop users (including Responder).
ArcFM Desktop automatically sets ArcGIS Snapping to use "Classic Snapping" in order to support ArcFM Snapping on ArcMap 10. The ArcGIS default snap environment is geometry-based and does not support granular subtype-to-subtype snapping rules that can be set in ArcFM Snapping (e.g., snapping between overhead line and overhead device).
If you want to disable Classic Snapping, follow the steps outlined below:
- Open the Registry and browse to the following location: HKEY_CURRENT_USER\Software\Miner and Miner\ArcFM8.
- If the Snapping key exists, select it. If not, right-click ArcFM8 and select New > Key and name it: Snapping.
- Right-click the Snapping key and select New > DWord Value.
- Name this new value: AutoEnableClassicSnapping.
- Right-click the AutoEnableClassicSnapping value and select Modify.
- Set the Value Data field to 0 to disable Classic Snapping. A value other than 0 in this field enables Classic Snapping. If this registry key doesn't exist, Classic Snapping is enabled by default.
- Click OK.
- Close the Registry.
Responder - Required Hotfixes
Applies to: Responder users only.
Hotfix: MXD files Upgraded to ArcGIS 10
Problem: ArcGIS Server provides MXD files through its web service to the Responder web browser. Multiple tools in the Responder web browser (e.g., map viewer and switch order requests) access these MXD files. The MXD files provided with an ArcGIS Server 9 release have in many cases stopped working after upgrading to ArcGIS 10 SP1. In some cases, certain point features can no longer be selected or identified after the upgrade.
Solution: Esri has corrected this issue with hotfix QFE-SGIS-10SP1-180571. Once you've installed this hotfix, add the following property to the "Properties" tag in the .cfg file associated with that specific map service. More information about the hotfix.
Hotfix: Labels on XY Event Tables
Problem: Drawing errors occur in ArcMap when lables exist on XY event tables.
Solution: Esri has corrected this issue with hotfix that will be available with 10 SP2.
Upgrade Fiber Manager
Applies to: Fiber Manager users only.
If you're upgrading your Fiber Manager schematics from 9.3.1 to 10.0.1, there are some steps that must be performed BEFORE you upgrade the geodatabase to 10.0.1.
Upgrade ArcFM Geodatabase
Applies to: All geodatabases being upgraded.
Upgrade your geodatabase before performing any other upgrades. If you are skipping release versions (e.g., upgrading from 9.3 to 10.1), you must perform the upgrade steps for each release in between your original release and the one to which you're upgrading. The exceptions are the Create/Update ArcFM Solution System Tables and Upgrade ArcFM Solution Database tools. These need only be run once with each upgrade, regardless of whether you're skipping versions.
- Execute the Create/Update ArcFM Solution System Tables tool with each upgrade. The ArcFM System Tables must be located in the same schema as the SDE system tables. When running this tool, you must be connected to the geodatabase as the user who owns the .Default version. All other users must be disconnected from the database. Running this tool is required.
- Use the Upgrade ArcFM Solution Database button to update your geodatabase with modifications required by the latest release. This button remains enabled on the ArcFM Solution toolbar in ArcCatalog. You must be signed in as the owner of the business data to upgrade the database, and you must be connected to an editable version. This tool also requires that there be a single owner for all GIS tables. This tool also performs the following updates:
- Updates the build number in the MM_PERSIST_INFO table to ensure all ArcFM tools in ArcCatalog execute properly with the new release.
Upgrade Steps in Past Releases