Latest Contributions by AllisonMuise1

FYI: The State Gov't  Solutions team has a Restaurant Inspections solution that may help: Restaurant Inspections | ArcGIS for State Government  ... View more

monzay‌ When you set a filter in a web map using the 'Ask for Values' option, you are forced to declare what the initial filter value will be. In many cases, it is more helpful to have the application load showing all records and then have the user apply the filters as needed than to have the app load pre-filtered. For example, in my organization my data managers might need to filter the data to look at records with a specific values in the following fields: STATUS (which contains the values 'open', 'in progress', and 'closed'), ASSIGNEDTO (which contains the values 'Mark', 'Joe', 'Sarah', 'Amy') TYPE field (which contains the values 'streets', 'parks', 'utilities') When I set up my map, I have to set filters on these fields that point to specific values ( STATUS='open', ASSIGNEDTO='Mark', TYPE='streets') and all three filters will be applied concurrently to the layer. In Manager I want to have access to filters on all these fields, but it's rare that I'll want all three applied concurrently and I don't want the app to open with such a restricted view of the data. This is where that app configuration setting comes in. By telling the app to ignore those initial filter values, the application will open with all the data visible and I can then gset the filters (by clicking the field header) that are specific to my tasks - perhaps seeing all reports that are open or in progress, or looking to see what work someone was assigned so that it can be reassigned, etc. Without that setting, the application is always going to load showing me only the reports that meet the criteria of that initial filter setting - open street reports that are assigned to Mark - even if there aren't any - and I'll need to go clear/update the filter values to see other views of the data. This setting DOES NOT affect any static filters you apply - ones without the 'Ask for Values' option checked. -Allison ... View more

monzay‌ When Reporter loads, your browser should ask you if you'd like to share your location.  If you share your location, the reports list returns the features by order of proximity to the location provided by your browser. The reports are only sorted in the order they were created when your location is not shared. If your browser does not ask you this question when the app loads, it is likely that you told it to never ask you that question again for this app and you'll need to clear your app URL from that list in your browser settings. For example, in Chrome this setting is under Settings> Advanced Settings>Privacy-Content Settings>Location>Manage Exceptions In our testing, these were the only two sort options requested, but we are open to suggestions of alternatives. Could you elaborate more on how sorting by a field such as status would help the end users of your Reporter configuration? ... View more

Thanks for the idea! I can see where this would be helpful in many cases. I've added this suggestion to the backlog for this application. ... View more

pemcbride‌: Can you share the URL to your application? You are correct that Manager should show the related records. I haven't seen this before and it will be easier for me to troubleshoot if I can see what's goign on myself. -Allison ... View more

I think the app should handle the mixed coordinate systems, but I agree that ruling that out is a good place to start. You might also consider calling Support. They'll be able to help you troubleshoot this much better than I can on these forums. They'll also be able to log any bugs found during that process. ... View more

hmm... What tiling scheme did you use for your basemaps? Are there any errors reported in the browser console? ... View more

Jesse Mardis‌ It is very hard to suggest a strategy without in-depth knowledge of your existing infrastructure and your near and long-term goals. Based on what you've described above, I suggest keeping your work in SQL Server unless you run into something that requires you to work in FGDB. We ship an FGDB just because that is the easiest way to package up the content o deliver it to you. How exactly you go about this is a decision that will be unique to each organization. I recommend a careful read of the documentation here: Local Government Information Model | ArcGIS for Local Government . There are links to tools that will help you migrate an update, and also some discussion on the Get Started - Overview page of strategies for migrating. There are also some good videos on E380 that might help you decide how to proceed. Here's one example: Home | Esri Video  The simplest strategy - in my opinion - is to pick a solution that will help your organization in some way, and to start there. Organize the few datasets that are needed for that solution, build out the maps and apps, and then move on to the next one. Working in small chunks like this will be a lot simpler than biting off the whole LGIM and you get results in the form of a workflow or app very quickly. The end goal of the LGIM is, after all, to help you organize your content so that it is more usable. ... View more

Allen Scully‌ It sounds like your basemaps don't extend to the zoom level the apps is using to display the parcels. Try adjusting the ZoomLevel parameter value in config.js to a level where your basemaps will draw. ... View more

Yay! Glad that helped. I also write the doc for these apps so I'll take a look to see if I can clarify that language a bit, too. ... View more

I think your instincts are right on the comments - something is not quite right with the relationship between the features and the comments table. 1. The relationship must be a one-to-many relationship based on a relationship class created in a gdb prior to publishing 2. The primary key field on the feature layer must contain a unique value for each feature. I don't recommend using the OBJECTID feature for this as those values are subject to change if you move features into a new dataset. I suggest using a Global ID field or other field (footpath ID, footpath name) etc that contains unique values. 3. The foreign key field on the table must be of a type that can receive the values from the primary key field. No other values should be automatically written to this field. For these reasons, the foreign key should NEVER be an OBJECTID or Global ID field. If the primary key is a Global ID, the foreign key must be a Guid field. Currently users cannot attach documents with their comments but this is coming in the December release of AGOL. If your feature layer currently has attachments on the table, you won't need to do anything to expose this functionality after this release a 'Browse' button will be automatically added to your comment form. ... View more

Robin Patton‌ I don't have one, but it would be fairly easy for you to set up. 1. Create a group in your organization, and create an app from that group. Don't worry about the configuration options for now - you can always come back to them later. 2. Add an editable polygon and/or line layer to a map, save the map, and share it with the group that you created in the previous step. 3. Open the app and sign in to the app using the AGOL sign in button (unless you've also shared the app, map, and layer(s) with Everyone in which case you can use Guest), and submit a report. ... View more

Another option for crowdsourcing lines and polygons is the Crowdsource Reporter web app template Crowdsource Reporter | ArcGIS for Local Government  ... View more

I've verified that a fix for this will be included in the next release. With the next AGOL release, feature collections will be supported as reference layers in Crowdsource Reporter. ... View more