Wenn ich Beispiel-Utility Network-Datenmodelle in ArcGIS Pro vergleiche, ist mir aufgefallen, dass Version 3.2 einige zusätzliche unterstützende Tabellen wie D_rename enthält, während diese Art von Tabellen im 3.3 Modell fehlen. Wird es Probleme verursachen, wenn ich diese älteren Tabellen, wie D_rename aus Version 3.2, mit dem 3.3 Datenmodell verwende? Sind diese Utility Network-Versionen auch an bestimmte Versionen von ArcGIS Pro oder ArcGIS Enterprise gebunden? Falls ich meine Enterprise-Version später aktualisiere, könnte das möglicherweise eine Utility Network, die mit einer älteren Version erstellt wurde, beschädigen oder Probleme verursachen?

Regarding the D_ tables, yes, it is possible to use older D_ tables with a newer schema. A word of caution though. The newer schema is likely different from the older schema, and the configuration and rename may not give you the results you are expecting because of this difference. You can and should do an update of these tables and review them for changes in the schema. The suggested workflow would be as follows: * Add the older D_ tables to the newer asset package * Run the Create Rename Table tool in the Utility Network Package Tools toolbox.* Specify only the asset package parameter. Do not enter anything in the rename fields. This will update the rename table against the new schema while retaining any previously set values. * Run the Create Configurations Table tool in the Utility Network Package Tools toolbox.* Specify only the asset package parameter. Do not enter anything in the configurations fields. This will update the configuration table against the new schema while retaining any previously set values. * Review the updated D_ tables and make changes as you see fit. * Use the Config and/or Rename tables when applying the asset package.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Utility Network Datenmodell-Version

EsraCındır

Wenn ich Beispiel-Utility Network-Datenmodelle in ArcGIS Pro vergleiche, ist mir aufgefallen, dass Version 3.2 einige zusätzliche unterstützende Tabellen wie D_rename enthält, während diese Art von Tabellen im 3.3 Modell fehlen.<\/P>

Wird es Probleme verursachen, wenn ich diese älteren Tabellen, wie D_rename aus Version 3.2, mit dem 3.3 Datenmodell verwende?<\/P>

Sind diese Utility Network-Versionen auch an bestimmte Versionen von ArcGIS Pro oder ArcGIS Enterprise gebunden? Falls ich meine Enterprise-Version später aktualisiere, könnte das möglicherweise eine Utility Network, die mit einer älteren Version erstellt wurde, beschädigen oder Probleme verursachen?<\/P>

Finde mehr Beiträge mit dem Tag

Wastewater

Water Distribution

Network Management

Accepted answers

PatrickGCowan

Regarding the D_ tables, yes, it is possible to use older D_ tables with a newer schema. A word of caution though. The newer schema is likely different from the older schema, and the configuration and rename may not give you the results you are expecting because of this difference. You can and should do an update of these tables and review them for changes in the schema.

The suggested workflow would be as follows:

Add the older D_ tables to the newer asset package
Run the Create Rename Table tool in the Utility Network Package Tools toolbox.
- Specify only the asset package parameter. Do not enter anything in the rename fields. This will update the rename table against the new schema while retaining any previously set values.
Run the Create Configurations Table tool in the Utility Network Package Tools toolbox.
- Specify only the asset package parameter. Do not enter anything in the configurations fields. This will update the configuration table against the new schema while retaining any previously set values.
Review the updated D_ tables and make changes as you see fit.
Use the Config and/or Rename tables when applying the asset package.

All comments

EsraCındır

Thanks @PatrickGCowan, i will try your workflow suggestion.

PatrickGCowan

The suggested workflow would be as follows:

Add the older D_ tables to the newer asset package
Run the Create Rename Table tool in the Utility Network Package Tools toolbox.
- Specify only the asset package parameter. Do not enter anything in the rename fields. This will update the rename table against the new schema while retaining any previously set values.
Run the Create Configurations Table tool in the Utility Network Package Tools toolbox.
- Specify only the asset package parameter. Do not enter anything in the configurations fields. This will update the configuration table against the new schema while retaining any previously set values.
Review the updated D_ tables and make changes as you see fit.
Use the Config and/or Rename tables when applying the asset package.

Ayan Palit

@EsraCındır There is definite Utility network compatibility to ArcGIS Pro and ArcGIS Enterprise.

As a general rule for working with mixed releases and the utility network, ArcGIS client applications (such as ArcGIS Pro and ArcGIS Enterprise) are backward compatible. However, best practice is to align with the Network Management Release Plan

The Utility Network schema changes are tied to functionality and documented at the Utility Network Foundation solution release notes. You can review Water Utility Network Foundation Release notes

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.