Latest Contributions by RobbHodges

Are you searching numerical fields? Most of our searches are on GIS IDs for our features that are all integer fields. None of them seem to have the behavior that you are describing. I did find that for the couple of fields that are text based, we are also getting the same results as you are.  What about your field values...are they populating? Some seem to work, while others don't. Fields that are auto-created when you enable editor tracking seem to work. Most, however, do not populate (searches do not work on these). I thought it had something to do with the field alias issue, but that doesn't seem to hold true, because I have fields that follow that rule, but do not populate.  I really wish they would just re-release the older, working version. It's been 3 weeks now and it still doesn't look like a permanent, working fix is coming out soon.  ... View more

Just installed the latest test flight update (just came through maybe 10 minutes ago). This is another step back. The group layers still work. That's good. The fields are back to not working properly again, just like they did when the 17.0 update came out. Feature searches are still not working. Most fields do not populate. The date field seems to be working again, but at this point I'd rather it not work and the other fields do work.  ... View more

I'm sure that everyone is working hard at trying to find solutions to these problems, and I appreciate that. However, these problems existed in the beta. They are causing a lot of problems for us. As someone else here said, the trust we had worked to build up with many of our users, is quickly eroding. I understand that with the conference and the new markup tool there was likely a lot of excitement about releasing it right away. I really hope this never happens with collector. After shifting so many of our collection processes over to the collector app, it would eliminate any trust with using GIS to gather information in the future. I really hope that this is a lesson learned that you have many types of users with many different setups. I know you can't cater to everyone, but it seems as though this was a pretty widespread. Again, I get that everyone is likely working hard to resolve these issues, but they should have been resolved before this app was released. Hopefully more folks will use the betas from here on out and report these problems so that we aren't in the same predicament next time.  ... View more

It is happening with a 10.5.1 layer.  ... View more

So in 17.1.1 the group layers appear to be working. Doing feature searches still don’t work. I’ve also noticed that the date fields show up incorrectly. That’s new to this update. I’m also still noticing that at times, it takes unusually long to get the popup to come up.  ... View more

I had to request the 17.1.1 separately from 17.1.0.  ... View more

We're in a similar boat. I don't have quite that many users (at least not for the explorer app), but most that I do have were a bit apprehensive about using it in the first place. We've finally come to a place where everyone is doing well with it and then this release drops. I had seen these issues in the beta about a month ago and was told they were looking into it. I hope they get this resolved in a hurry, because it's become somewhat of a big issue for us.  ... View more

Here is a list of the 3 bugs I reported yesterday....they all seem related from what we can tell.  #BUG-000106480 - popups not working (the popups seemed fine for features that did not participate in a group layer. I assume as Justin said, we could probably change the alias to match the field name and it would work.) #BUG-000106475 - Search not working (we noticed features not in a group layer worked fine regarding search...the ones in a group layer did not work.) #BUG-000106474 - unable to toggle sub-layers on or off (only the group shows) To Jeff: I am also seeing that the feature attachments are not working. ... View more

It says that it was fixed in the latest version. We are still having this issue. Has it been fixed for anyone else? ... View more

You may actually be interested in a new tool they've developed called survey123. I haven't had a chance to try it yet, but we have a similar situation with some of the things that we collect (multiple options for a question). This will allow you to do that. Survey123 for ArcGIS ... View more

Again. It works when it's the only feature service in the map. The valve inspection solution uses a similar example with the facility ID. -Robb Hodges ... View more

Well, it works every time when it's the only service I'm the webmap. When there are other services, it's hit or miss. -Robb Hodges ... View more

I am using a related table to store valve inspections. When create a new inspection, it uses the relationship from my valve features to populate the valve facility ID in the related table. Sometimes it does this correctly. Most of the time, it tries to use GPS to capture the inspection, bypassing the relationship. I that case, it doesn't populate the table with the valve facility id. In fact, it doesn't let me fill out any attributes in the related table. I can't turn off the GPS. It defaults back to turning the GPS on. I tried that already. All the data is hosted on our server. ... View more