Latest Contributions by ChrisFox

Hi Sara, I would add that you don't have to use the other apps to set those values in the fields. That is the way the solution was designed, but if you just edit the InfrastructureProjects feature in a Web Map, Pro, etc. and set those values on the fields the features will show up in the Dashboard. So it is possible to just use the Dashboard and ignore the other apps if they are not required in your workflow. ... View more

Hi Ashlie, Yes, the web map viewer makes this a little confusing. It will override the feature templates defined on the layer in the feature service to match the symbology in the map. Citizen Problem Reporter, however, will honor the template defined on the layer in the feature service. So you can temporarily change the symbology in the web map to single symbol just so you can edit the feature template on the service, you can then change the symbology back without impacting the feature service template and Problem Reporter should behave as expected. If you would prefer this is actually easier to do through the REST admin api on the feature service: Go to the REST end point of the service and in the url between rest/services add admin, /rest/admin/services/ and hit enter At the bottom of the page, click updateDefinition Copy the JSON below and paste it over all the JSON in the Update Layer Definition box. You can replace "My Category" with the category you want to use. Click Update Layer Definition { "templates" : [ { "name" : "Problem Report", "description" : "", "drawingTool" : "esriFeatureEditToolPoint", "prototype" : { "attributes" : { "category" : "My Category", "publicview" : "Yes", "status" : "Submitted" } } } ] } ... View more

Hi Ashlie, The Crowdsource Reporter application uses the editing feature template associated with the layer to set the default value when creating a new feature. So you will need to update the view's feature template to set the default value for the Category field. To do this: In the CitizenProblems layer update the Category domain to add your new value Create a view of the CitizenProblems layer for your new category. Add your view to a new web map with full editing control Change the symbology to location only - single symbol Click Edit and at the bottom of the Add Features panel click Manage Click the dropdown next to your Feature Template and select Properties Select the category for the view and ensure status is set to Submitted and click Done Click Save Changes to update the feature template. -Chris ... View more

Hi Sara, Project Plans need to have the Funded field set to 'Yes' and Project Status set to 'Board Authorized' to show in the dashboard. The best application to set these is with the Capital Project Review application. To have projects show up in Capital Project Review you need to set the Project Status to "Analysis and Review". Capital Project Plans was designed to be used by by project leads to organize new capital project plans and revise project information during the planning process. Capital Project Dashboard is designed to show projects that have been approved and funded. This is why the dashboard filters out projects that are still in the planning phase, planners will iterate on designs, update schedule and costs estimates, etc. When they are ready for review the status is updated to "Analysis and Review". In review, if approved a funding source and fiscal year will be set, before ultimately be marked as funded and approved. I agree that the documentation here is lacking. We do have plans to include more documentation and potentially a learn lesson that describes how the applications work together and how a project plan moves through the process. Regards, -Chris ... View more

These issue seems to occur when the service editor setting 'What kind of editing is allowed?' is set to 'Add features'. If you set it to 'Add and update features' it adds the Uploads capability and you can successfully submit the survey with attachments. I have updated this on the ROW Permit solution and if you re-deploy the Solution you will get this setting and it should work in Portal. ... View more

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