Select to view content in your preferred language

I need help with upgrading Lead Service Line Inventory Solution Version 2.0 to 3.0

831
9
Jump to solution
09-27-2023 11:22 AM
DustinHuff8
New Contributor

Hello, I am newer to GIS and using solutions, but I have set up and we have been using version 2.0 of the Lead Service Line Inventory Solution since roughly October of 2022.  I saw the post about upgrading to Version 3.0, but in the steps it just talks about coming from version 2.1 or 2.2, not 2.0.  We have collected and input a bunch of data so honestly I'm scared to try anything without knowing for sure if it will mess anything up or not.  We are wanting to upgrade to version 3.0 to meet the EPA requirements, is there anyone that could help me with the steps of what I need to do so that we can get set up in version 3.0?  I do not believe that we made any modifications to the version 2.0.  Thanks in advance for any help.

0 Kudos
1 Solution

Accepted Solutions
AlexKabak
Esri Contributor

Hi Dustin,

The Upgrading to Lead Service Line Inventory 3.0 blog can be applied to moving from version 2.0 to 3.0.  Version 2.1 and 2.2 are mentioned in a specific step because they include a few items that are reused in version 3.0, and that step informs the user they will need to move those items to the new folder. Version 2.0 does not include those items so you do not need to worry about that step. 

As for the concern of breaking anything you have already built, when you deploy version 3.0 (the newest version) you will get a new folder with all new items so your existing version will not be affected. Your data can then be migrated into the new version.

Sorry about the confusion stemming from the blog, hopefully this clears things up.  

View solution in original post

0 Kudos
9 Replies
AlexKabak
Esri Contributor

Hi Dustin,

The Upgrading to Lead Service Line Inventory 3.0 blog can be applied to moving from version 2.0 to 3.0.  Version 2.1 and 2.2 are mentioned in a specific step because they include a few items that are reused in version 3.0, and that step informs the user they will need to move those items to the new folder. Version 2.0 does not include those items so you do not need to worry about that step. 

As for the concern of breaking anything you have already built, when you deploy version 3.0 (the newest version) you will get a new folder with all new items so your existing version will not be affected. Your data can then be migrated into the new version.

Sorry about the confusion stemming from the blog, hopefully this clears things up.  

0 Kudos
RichardFreer2
Occasional Contributor

I have been trying to upgrade from version 2.1 to 3.0 but I am unable to create a data loading workspace from arcgis online datasets.  It keeps giving an error when running the create data loading workspace tool, that no workspace was created because there were no matches.  The 2.1 version is out-of-the-box, no changes made to the schema, so it should have matches.  If I export the feature classes to a file geodatabase, and run the tool, it has no issues.  Any advice on how to get the data loading workspace to work with the hosted feature classes in arcgis online?

0 Kudos
AlexKabak
Esri Contributor

Hi Richard, 

What version of ArcGIS Pro are you using?

0 Kudos
RichardFreer2
Occasional Contributor

ArcGIS Pro 3.1.5

0 Kudos
AlexKabak
Esri Contributor

Can you please provide the parameters and error message as well? A common occurance we've seen is pointing only to the feature service and not the layer within the feature service. The source and target url's should end in a "/n" with n representing the layer id.

0 Kudos
RichardFreer2
Occasional Contributor

Create Data Loading Workspace
=====================
Parameters

Source to Target Mapping https://services5.arcgis.com/00hUnoewKbhedDpg/arcgis/rest/services/ServiceLine_d7ec844a2d354b33a4695... https://services5.arcgis.com/00hUnoewKbhedDpg/arcgis/rest/services/ServiceLine_d619965624b2452a8931c...
Output Folder C:\Users\rfreer\Documents\ArcGIS\Projects\Lead Service Line Upgrade
Calculate Feature Count Statistics true
Data Loading Workspace
Predictive Field Matching Options MATCH_FIELDS;MATCH_VALUES
Predefined Mapping Create_Data_Loading_Workspace_Predefined_Mapping
Create Matches by Subtype true
=====================
Messages

Start Time: Monday, July 29, 2024 7:24:32 AM
ArcGIS Pro 3.1.5.41833
dltsolutions 3.1.3
An output was not created due to no matches being found in the Source to Target Mapping parameter.
Succeeded at Monday, July 29, 2024 7:24:33 AM (Elapsed Time: 1.15 seconds)

0 Kudos
AlexKabak
Esri Contributor

Yes, your source and target url's are ending in FeatureServer when they should end in FeatureServer/n, with n representing the layer id. If you are copying and pasting the url in, ensure you are doing so from the layer. An easy way to get there is by clicking the layer on Feature Service item Overview page and copying the url from there. I have attached an image highlighting where to find the layer. 

AlexKabak_1-1722268077086.png

 

0 Kudos
RichardFreer2
Occasional Contributor

Thank you Alex, I will give it a go and let you know if there are any issues.  I don't remember having this much difficulty when I configured the 2.1 version, and it has been definitely stumping me.  When watching what videos are out there, they go through that portion of dragging and dropping the url into the dialog boxes so fast, you don't pick up on this important fact.

0 Kudos
RichardFreer2
Occasional Contributor

Thanks again Alex, that solved the issue.  Have a great week.

0 Kudos