Latest Contributions by KhaledHassen

Sorry for the confusion. We will get handled. The definition is mainly owned by the feature service and the runtime originally developed based on server. This is new in online and it looks like we have some differences in the case of the types. Runtime team does not define what the subtype json is and they have been involved in testing but it looks like this issue is not detected. The main reason I have mentioned about the collector is that we have recently fixed an issue that affected collector and was related to subtype default. I wanted to know the severity of the issue and if we need to handle it before Sept. release. If this issue is critical to you, pl. submit a request for us to the tech support (online feature service) and I will see if we can speed up the deployment.  ... View more

I am the online feature service lead but working closely with the collector app team which seems do not have this issue. At any case, I will fix this in the online feature service by Sept. Will touch base with the collector app to see if they have this issue. Khaled ... View more

Will fix it in online sept. release. What app has this issue? most of our apps (mainly mobile) work fine maybe because the check is case-insensitive. Until I get the fix in, pl. use case insensitive check if possible. Thanks Khaled ... View more

FYI we are working hard in online to get webhooks added to online feature service. We are trying to avoid having our clients to keep/making polling requests to our server looking for updates and the solution will not scale eventually. Online target online Dec. online release. If we will able to release sooner, we will let you know. Thanks Khaled ... View more

Even download sync direction is not supported on view join layer. We are working on a snapshot sync direction that can be supported on join view layer. But no timeline for this enhancement yet. Khaled ... View more

Hi Jimmy, I do not really see any solution except turning off the sync for the join layer in the map (if supported). Will be meeting with the offline team to see if we have a way to address this in the client side. Will update you shortly. I might also need to do some design change in the feature service to avoid returning sync errors in the join feature service view. Normally the client side (collector/etc.) keeps syncing even if one of the layers returns sync errors. Will be good if there is a way to turn off sync errors for the join layer. Khaled ... View more

Jimmy, It looks like you might need to turn off sync in the collector for the join view service or customize the list of the layers to sync. Even though there might not be any edits, collector might try to sync its content with server data.  Khaled ... View more

Try to set the capabilities instead in the feature service admin API. It would do that same. Not sure if we have an issue with syncEnabled property. SyncEnabled property is the old way of enabling sync. ../rest/admin/services/testSubtype/FeatureServer/updateDefinition Json: {"hasStaticData" : false, "capabilities" : "Query,Sync"} Khaled ... View more

I mean only the join view layer. All other non-join layers should be fine and be able to sync. ... View more

Thanks Jimmy. >It is strictly for display, no editing. The only issue I see here is that you will not be able to sync the offline from the join view. For instance, you will not be able to update your offline map from the joined view. I am assuming you are creating offline from the join view.  Thanks Khaled ... View more

Hi Jimmy, Not sure why you need to enable sync on the join views? We do not support editing of join view yet. So even though you might be able to enable sync on join views between two services, you will not be able to edit them or apply any edits from offline maps. Extracting changes from join views to offline map is not supported currently. Until it is fully supported on the server, I will not pursue sync for joined views. Join views should be updated though without enabling sync on the join view when the source data changes. Thanks Khaled Hassen ... View more

Yes you can use Pro and multi select the features and delete them. The main entry point to delete features is the REST API deleteFeatures. You can navigate to the service directory and apply your edits in the REST endpoints directly also (preferred). http://serviceUrl/rest/services/<serviceName>/FeatureServer/0/deleteFeatures?token=aaaaa You can delete by the list of ids such as [2,4,5, ...]. You can also specify a where clause to delete such as ObjectId > 2000. You might need to be chunk your deleted to avoid timeouts. Like deleting 200 features at a time. >The other thing I was wondering is if I could temporarily change the Edit settings of the hosted feature layer to "Add, >update, and delete features" without affecting the offline caches my field workers have locally on their devices.  Yes you can. This should not affect the offline map you have with the workers. Adding more capabilities are OK. Removing capability is the one that might affect your workers. Khaled Hassen Online Hosted Feature Service Dev Lead ... View more

Hi Kevin, We definitely preserve GlobalId when exporting. So you should see the same GlobalId in the filegdb. How did you append? from UX. Pl. be sure to use upsert=true to preserve the globalId. upsert is true from the ux when you choose updateExistingData. Khaled  ... View more

Hi Kevin, You still can use append from the filegdb with the old schema to the new service with the new schema. You can map fields by name in append. For fields with different types, we do map the old type to the new types as long as the two types are compatible. So old field of type short can be mapped to a new field of type int, etc. Khaled Hassen ... View more