Latest Contributions by JimmyKnowles

Mike Minami I'm in the same position as OP. I have a GUID field that refuses to show up in the Data tab from the item page and in the attribute table in the map viewer. I have confirmed the pop-up configuration in both the visualization tab and in the map viewer pop-up configuration. GUID field shows up fine in attribute table in Pro. I've looked at the feature service JSON in ago-assistant and everything looks good. When I go to Data->Show/Hide Columns or Show Table->Attribute Table->, the column isn't even there to make visible. Any ideas? ... View more

This would be unfortunate if this same intermittent error is occurring on iOS version of new Collector. Carl, could you provide more details to see if this is the same issue? A screenshot or exact verbiage would be nice along with circumstances when the error occurred. We had two field crews that were plagued by this error this past field season (Android, current version of Collector, 18.0.3). I submitted a support ticket, but due to the intermittent nature of this issue, we didn't get anywhere. I've experienced the error personally once, but have not been able to recreate it. I've literally spent hours downloading offline maps, creating features, and removing the map in hopes of the error happening to me again. I wasn't entirely pleased with support's troubleshooting logic, so just closed the ticket. I asked for a version of Collector with logging enabled (something that is available on the current iOS version), but they thought it made more sense to recreate the feature service and use process of elimination to try and find what was causing the error. But since the error is so hard to recreate, I didn't think we were going to get anywhere with their approach. I was hopeful that this would just disappear when Aurora for Android gets out of Beta, but now I'm a little worried with this latest news from Carl. Ronald Vanderpool, did you make any changes? Just curious if there's a reason why you haven't seen it pop up lately. Edit: One thing I should add is that the 'abort due to constraint violation' error is normally preceded by an 'unable to open file database' error. ... View more

I agree with you Ronald... intermittent and non-reproducible errors are the toughest to crack. This error has been popping up on us on different Android devices and different versions of Collector Classic. We've yet to see it in the iOS version. It is pretty frustrating since it can make a scheduled day of field work almost wasted. Hoping that someone figures it out or future updates fix it. Thanks for sharing your pain. ... View more

Got it Khaled. Thanks for the info. That makes sense. Just trying to wrap my head around how everything works internally. ... View more

So here's something that I just discovered. For each offline map in Collector, there's an info.json file. When I look at this file, it appears that the client (Collector) does set the sync direction by layer ('keyLayerSyncDirections'). For the join views in question, the sync direction is set to download, so not sure why these join views are generating sync errors.  ... View more

We have experienced this same issue and have been unable to figure out why as well. This issue appears to surface randomly and only affects certain editable features in the web map. Other features can still be created. I've looked at the .geodatabase files and nothing jumps out at me. You'd think a constraint violation would have something to do with a unique primary key, but that doesn't seem to be the case here. I've also tried to find a way to turn on logging in Collector, but haven't found anything. ... View more

Hi Kanchana, I fully understand that I can't edit the join layer. Yes, the difference b/w my use case and yours is that I am making edits to other feature layers in the same web map that the join layers are in and my need to sync is what is causing the sync errors. I have confirmed this by doing what you said. I created a dummy feature service and a new join which I enabled sync on. I then added both to a new web map to confirm the behavior. In the Android version of Collector, the error provides which layer is not syncing and it is the join layer. It appears that Collector still tries to run the synchronizeReplica operation on the join layer even though it is not editable and there are obviously no edits. I tried to disable editing on the join layer to force Collector not to run the synchronizeReplica operation, but this doesn't appear to work either. It looks like the web map disables editing by adding a capabilities property to the layer in the operationalLayers object. "capabilities": "Query,Extract,Sync,ChangeTracking" When I add a capabilities property to the join layers in the operationalLayers object, I either can't download the map or it still errors when syncing. I've tried it without 'ChangeTracking' as well since ChangeTracking would not be a valid capability for the join layer, but it didn't work either.  As I mentioned in my response to Khaled, I think my best course of action is just to live with the errors for now. Thanks again for your help. ... View more

Thanks for the additional info Khaled. I've come to the conclusion that the client application (Collector in this case) does not allow for per layer sync direction control. It only allows some control on editableLayers and readonlyLayers, but not on individual layers.  I think my best course of action is to implement as desired and ignore the errors for now. I'd be interested in hearing if any changes are made either on the client or server side. Thanks again for all your assistance. ... View more

Thanks Kanchana. I looked through the pdf you shared and have been able to replicate everything outlined there. With Khaled's help, I was able to enable sync on all the join views (it appears that the procedure has changed slightly). On the web map, the offline settings now show up under the item settings and 'Use in Collector for ArcGIS' is also there. I am able to download the web map, but when I sync the map I'm getting sync errors. I think this is where your workflow is different than mine. I am making edits in Collector and based on your pdf, it looks like you're using S123 to make edits. Since there are edits made in Collector, I want to be able to sync these edits. The edits seem to sync fine, but I'm getting errors since Collector is trying to sync these join views which are not technically syncable. My join view has the following, which leads me to believe that I should be able to set the sync direction to download. "supportsSyncDirectionControl" : true, This setting allows the client application to set the sync direction, but I can't find in Collector where I would be able to set the sync direction. I guess an option is just to live with the sync errors since the actual edits are syncing fine. Any ideas on how to get rid of the errors? ... View more

Khaled, thanks for the suggestion, but that doesn't seem to work. Or at least the way I tried to do it didn't work. I used ago-assistant to edit the json of my web map for use in Collector. I modified the capabilities of the join view layers. I tried both "Query, Extract" and "Query, Extract, Sync". When I do "Query, Extract", the web map will not download in Collector. When I use "Query, Extract, Sync", I'm getting "Unable to synchronize replica" errors. Any other suggestions? I read through most of the web map json spec and didn't find anything else. Kanchana Karthikeyan‌ - did you have any of these issues when you implemented this? ... View more

Sorry to bother you guys again, but I'm getting 'sync replica internal error' when trying to sync. The syncs on all the other feature layers seem to be working fine, but Collector is returning this error on the dynamic join views. It seems that Collector is trying to sync these feature servers even though it is uneditable and there are no edits. I looked through all the other feature server properties and nothing jumped out at me that would tell Collector this is a download only sync (maybe set supportsAppend to false??). It seems like syncDirection is used when creating a replica, but is not a property of the feature server. Any ideas?   I did try enabling the 'Push Only' setting in Collector, but that didn't seem to help. ... View more

That did the trick Khaled. I really appreciate your help. ... View more

Kanchana, just want to make sure I'm following the same procedure as you. I went to updateDefinition and added {"syncEnabled": true} Response was success and capabilities show "Query, Sync" for the feature service, but only show "Query" for the layer in the feature service. This seems to prevent me from taking the map offline. Any suggestions? I know this is an unsupported use of the join view, so understand if you can't help. ... View more

Thanks for the feedback Kanchana. That's the same thing I'm looking to do. Glad it works! ... View more