Latest Contributions by RyanKoschatzky

@TingWang1 Suggest logging an Esri support case and note that 'error msg' is misleading when using the right-click "Reconcile/Post" function from the "Manage Versions" window.  ... View more

OK thanks, I'll check with the rest of my team to see if they know of any way this would be locked - there were no internal locks for the database, and the server manger was where I disconnected all those services.  But there is a chance someone posted another service to a server I don't know about. ... View more

Brett, If you download the pdf and look at page 17 and 18 you should see the attached Poll Questions and responses. If you don't see, send me private message with your email and I can send you a copy. For each meeting, I have the RHUG slides followed by esri updates, the presenter for the month, comments from the chat and then polling responses if we have one.  ... View more

The bullets below are some concerns about branch versioning summarized after talking to some RHUG members.   Implementation of Quality Control (QC) via Branch Versioning The process for editing routes by some R&H clients relies on a three-tier versioning model as below that is based on traditional versioning. Tier 1: Default Version Tier 2: Quality Control (QC) Version; Child of Tier 1 Tier 3: Editor Version; Child of Tier 2 or Grandchild of Tier 1 At Tier 3 multiple editors can simultaneously perform edits to the networks managed in R&H; at Tier 2 there are at least one person performing QC and then posting and reconciling; additional QC may also occur at Tier 1 or the Default version. This three-tier or plus versioning model is a typical configuration for the R&H User Group (RHUG) members that had deployed R&H before the ArcGIS Pro based R&H extension became available and functionally ready. A workaround solution for implementing the complete set of requirements for QC in the ArcGIS Pro based R&H environment will simplify the process for such RHUS members to migrate and speed up the migration.   System Integration in ArcGIS Pro based R&H environment Current efforts to implement system integration are based on traditional versioning.  The AgileAssets’ LRS Gateway is a typical example.  Without traditional versioning in the ArcGIS Pro based R&H environment, those RHUG members that are working on system integration may have to extend their effort tweaking and testing their solutions in the new environment, which is a risk that the members may have to take.  It may further delay the migration from ArcGIS Desktop to ArcPro for such RHUG members.   Integration with Other Esri ArcGIS Applications   In the ArcGIS Desktop platform, such ArcGIS products as Workflow Manager and Data Reviewer can integrate well with R&H so certain workflows can be set up and executed in a seamless way. Some RHUG members (for example, West Virginia DOT) have their R&H editing workflow configured with the three applications integrated.   In the ArcGIS Pro platform, the R&H extension is service oriented, so how will it integrate with Workflow Manager, Data Reviewer, and other ArcGIS applications?   Impact on Data Recovery The branch versioning in the ArcGIS Pro based R&H environment means that there are only two levels of versions. In the case that there are many concurrent child versions or simultaneous editing activities (we don’t know yet what the breakpoint would be before a chaos should happen), the likelihood for mistakenly committing a change by any of the child versions to the default version, which must be set to public, would increase considerably. This may imply an unexpected increase in the roll back of the R&H transactional database.  To reduce the risk, RHUG members will probably have to increase the frequency of backing up the R&H transactional database and be prepared to redo those impacted editing jobs.   Other Ripple Effects Some RHUG members may have implemented certain business processes that depend on the concept of traditional versioning in the ArcGIS Desktop based R&H environment (it’s up to the members to report).  The switch from traditional versioning to branch versioning and the change in database schema may require such RHUG members to revisit, update, and reimplement the processes. One example is how to utilize a script to read the default version data from the R&H transactional database.  Compared to the ArcGIS Desktop based R&H environment, in the ArcGIS Pro environment there does not have Add/Delete tables anymore; all changes occur in the base table; all user edits are in one table with the BRANCH_ID defining which branch version is being edited.  The example illustrates the script should be updated before it can function properly again.     Yueming Wu @ West Virginia Department of Transportation ... View more

"Also, I am interested if there are any differences in output between the Arcmap and Pro versions. We have an external software that is completely reliant on this output." There is differences in the code that RHUG-AAGW has talked about but I don't know if anyone has tested to review the output at this time. I would recommend testing. That said it depends on what version/patch of R&H desktop your using as there was a bug found that SDE and FGDB exported different results. https://community.esri.com/t5/roads-and-highways-user-group-rhug-questions/export-network-bug-is-impacting-lrs-interface-to/m-p/1117095 Fixed in 10.7 Patch 3 https://support.esri.com/en/Products/Enterprise/arcgis-server/ArcGIS-Server/10-7-1#downloads?id=7940 Fixed in 10.8 Patch 2 https://support.esri.com/en/Products/Enterprise/arcgis-server/ArcGIS-Server/10-8-1#downloads?id=7941  Hope that helps and please share your testing results as many of us will be curious and will be doing similar testing within the coming years as we migrate to Pro. ... View more

Hi Graeme, This is a limitation within ArcGIS Pro.  We've made the decision to remove the link to the help all together to prevent any confusion for our users moving forward.  You'll see this change reflected in Pro 3.1. Nathan ArcGIS Roads and Highways team ... View more