Latest Contributions by ChrisFox

Hi Stephen, Thanks for testing the 'attachmentGroups' error from the original post was the error I remembered fixing in 1.5. This new error I haven't seen before and is also occurring when attempting to copy the data from the original service to the new service. I am wondering if the service is public or if you could invite my user (MapFox) to a group in your online organization so that I could debug the issue by attempting to clone to a Portal on my side. -Chris ... View more

Hi Stephen, What version of the api do you have installed? We fixed some things that may have caused this problem in 1.5 that was just released. -Chris ... View more

Eric, I have a bug logged and will be addressing it in the next release of the deployment tool..  ... View more

I found one workaround was to publish a new hosted feature service from Pro called DebrisReports_v2. It really can be any data just have to force a new service into the org with that name. Then if you deploy the solution it will see a service already exists with that name and give it a unique name which should resolve the issue. ... View more

If you do the same but give it a different title then DebrisReports_v2 does it work successfully? ... View more

Thanks Eric, I haven't found a specific organization setting that causes this issue. However, if you wanted to try a quick test it would help confirm if it was the same issue I have seen in the past: In the organization where it is failing, go to your content and click Create > Feature Layer Select From Url and paste the following url, https://services7.arcgis.com/GH2HnPU0MTsXT4xa/arcgis/rest/services/DebrisReports_v2/FeatureServer  Click Next through the next couple of pages, make the title of the item 'DebrisReports_v2' and give it any tag Click Done to create the service If the theory is right you will get an error because the org doesn't like the service name 'DebrisReports_v2'. I have found if you repeat the steps and change the title at step 3 it creates the service with no issues. ... View more

Hi Jennifer, Eric, I am wondering if this is happening for all solutions or just particular solutions? I just attempted to deploy Capital Project Dashboard to my org and everything worked successfully. I believe I have encountered this error in the past, but it only occurred in specific organization with a couple of the solutions. The issue occurred when the tool was attempting to create the hosted feature layer. I found the org didn't like the name of the layer even though a layer didn't already exist in the org with the same name. ... View more

Hi Ben, we don't have a way to leverage these already published layers . It is something we are thinking about how we can better support. The issue is if you published the layers using the same schema provided in the LGIM than everything should work, but if they don't then the maps and apps would likely be broken. ... View more

Hi Ben, The Solution Deployment Tool will create new feature layers if they haven't already been deployed using the tool. However, if you deploy a solution that for example uses the SiteAddresses layer today and then tomorrow you deploy another solution that uses the SiteAddresses layer it will not create another copy of the layer, it will reuse the one that was previously deployed. So you will not need to manage multiple version of the layer for each Solution. If you are seeing this please share the details of the Solutions that you deployed that resulted in multiple versions of the same layer as this would be a bug. The tool doesn't find layers that were published outside of the deployment tool, so it is true if you published a SiteAddresses or Parcels layer separately the deployment tool will create a new version which will be used in future deployments of Solutions. ... View more

Hi Cinthia, Domains are stored differently in hosted feature services than geodatabase feature classes. In hosted feature services every domain is defined and stored with the field. Although the domain has a name property different domains with the same name can exist in the same layer. So this is why the tool was written the way it is and asks you select the field you want to modify the domain for, rather than selecting the domain you want to modify as you would with a geodatabase. One thing you could try is run the tool 1x on a field. You can then see the result of that tool run in the Catalog pane and drag it into a new model. From model builder you could try adding a iterator to repeat for the all the fields with the same domain. ... View more

Hi James, As a troubleshooting step if you set copy_data=False during the clone does it work successfully? I am just curious if it is failing during the creation of the feature service or if the problem occurs when attempting to copy the data between the services. -Chris ... View more

I haven't done any performance testing in this regard, but my guess is it would be faster via .NET and the Pro api. This theory is simply based on the fact that there is some overhead in executing a GP tool. The things that are nice about GP such as parameter validation, messages, and cleanup when you are working with the tool through the UI can add a little time to each operation that you won't incur in .NET. ... View more

Hi Luke, This is certainly a supported approach if you want to include geoprocessing tools with your add-in. I have done this in a couple of my add-ins when I had existing geoprocessing tools that I leverage in other workflows but also want to invoke them from custom controls in the UI. To package the toolbox with the add-in you will want to add the .pyt to your project, set the build action to 'None' and the Copy to Output Directory to 'Copy always'. When you build the project the toolbox will be packaged with the add-in along with your \assembly and any other dependencies. In your add-in code you can then get the path to the toolbox on disk using the path of the executing assembly: string installPath = Path.GetDirectoryName(System.Reflection.Assembly.GetExecutingAssembly().Location); string toolboxPath = Path.Combine(installPath, "MyToolbox.pyt");‍‍‍‍ Now with the path to the toolbox you can either open the tool in the geoprocessing pane or execute the tool. ... View more

Hi Brian, Please check out the thread below. In it I describe how to author the pop-up and configure the arcade expressions to support the pop-up: https://community.esri.com/thread/207970-problem-with-the-capital-projects-solution-deployment-tool  I would also recommend leveraging the Solution Deployment Tool described in the getting started section of the help for the Capital Projects Dashboard solution. This will lay down the layers, webmap and dashboard in your org already configured with everything you need for the solution. ... View more

Hi Michael, You found a bug in the solution. The original intent was that you set the status to Analysis and Review in the Capital Project Plans. The project would then show up in Capital Project Review and you could use this application to set the Funded Project to 'Yes' and update the status to Board Authorized when it was ready to move forward. This field wasn't exposed in the application. I updated the this on our side so if you delete the Capital Project Review web map and web application and re-deploy Capital Project Review you will get the update. Otherwise you can edit the pop-up to make the field visible and editable and edit the Funding and Status widget to expose the Funded Project field. To edit data in the Capital Project Review select one of the drawing tools in the Funding and Status widget and select one of the projects. This will pop up a dialog where you can edit attributes on the feature. The nice thing about this widget is you can select multiple projects and update their status all at once and you can use the filters in the app to narrow down the visible projects. ... View more