|
POST
|
We have developed Append to deal with similar workflow like what you describe. We scale very well with the append API. The only other way to update the data which would definitely be more efficient to use sync and offline between online and the external system that updates the data. But this is not normally available specially if you are dealing with external data providers that use different system. Thanks Khaled Hassen
... View more
02-05-2019
07:28 AM
|
0
|
3
|
6788
|
|
POST
|
>I have an unique identifier which is a string and which is not available when I use the append function from AGOL. >Using AGOL I worry about two things: The key in the destination layer that you are using for upsert needs to have a unique index. This is why it does not show from the UX when appending from AGOL. The UX provides a way to add a unique index based on your unique field. >If different users are using different copies from the feature class to add features I guess it could happen that an Object >ID exists that is not the same feature as an Object ID among the new features. Thus it would be better to use our >unique identifier. Yes you cannot use the ObjectId for this. You have to either use a globalId or your own key that are the same in all copies. Copying data preserve within ArcGIS normally preserve GlobalIds, so duplicating data still reference the same feature. >My next problem is that I have to find a solution without the python API - could I put the same in a python script running >from ArcMap 10.6? You do not need to use Python API to do this. You can always use the feature service REST API to do this in any language. You can use fiddler to see how the home app uses the REST API to append data into online feature service. Thanks Khaled
... View more
02-05-2019
07:24 AM
|
1
|
0
|
6788
|
|
POST
|
You do not really need to do anything for the changes to be applied to the feature service after using append. If append succeeds, then new features will be appended and existing features will be updated (if you are using upsert). To update existing feature, you will need to use append matching key between the gdb feature class and the feature service layer. The online feature service layer field that is used as an append key needs to have a unique index in the online feature service layer. The online home app contains update data option where you can update the online layer from different sources. Pl. check it out there and see if the data is updated with the options you have chosen. Let us know if this does not work for you. Thanks Khaled Hassen
... View more
02-04-2019
07:49 AM
|
0
|
7
|
6788
|
|
POST
|
Yes we do support append API in online feature service. Also it is available in python API. Feature Service Append API Thanks Khaled Hassen
... View more
02-01-2019
08:36 AM
|
2
|
0
|
6788
|
|
POST
|
Yes this is currently a limitation in publishing with overwrite. Online team will work in removing this limitation in the next release or so. But I think we might need to consider using Append API with upsert capability. This where you get a chance to insert new data or update existing data from different sources based on the use of a unique column in the destination layer. Actually this is a better solution that keep overwriting your data from the same source regularly. Once you use append and update the source, existing views should continue working and picking up the new changes in the source data. Thanks Khaled Hassen
... View more
02-01-2019
08:31 AM
|
1
|
7
|
8662
|
|
POST
|
No it does not matter how you do the schema updates. UX schema updates call the low level REST API and this is where view refresh happens. Is it possible this is an old view you have created like a release or so ago? Can you try it on a new view and let me know?
... View more
01-24-2019
08:31 AM
|
0
|
0
|
4182
|
|
POST
|
Yes that is supported by default in all views.Schema changes like adding or dropping column in the source data will be propagated to all views. Also changing any field property like domains, alias would also be propagated to the views. Khaled Online feature service Dev. Lead
... View more
01-23-2019
06:57 AM
|
1
|
3
|
4181
|
|
POST
|
Online feature service supports reordering fields using views. You can always create a view layer based on a source layer. You can configure the view layer with any field ordering that are different from that of its source. With this solution, you would not need to do any work or ordering in the UX and you will persist your ordering in the server side. Ordering the fields in the view does not affect the source layer and the source layer will still be in the original source. Your maps would reference the view rather than the source. You can also select subset of the fields in the layer and you would not need to show all fields by marking them visible (true/false). Not sure if this is something you would like to pursue but it is an option we have in the server side. Thanks Khaled Hassen Online feature service lead
... View more
01-22-2019
03:50 PM
|
0
|
0
|
1099
|
|
POST
|
Eric, I see the GUID field is defined as editable=false { "name" : "reference", "type" : "esriFieldTypeGUID", "alias" : "reference", "sqlType" : "sqlTypeOther", "length" : 38, "nullable" : false, "editable" : false, "domain" : null, "defaultValue" : null }, The guid field needs to be editable. The Globald is the only field that needs to have editable=false. Sorry we do not have a way to change this property from the admin API. You can drop the relatiohship and the guid column and repeat the process . Will be good to start from scratch just to be sure all are good. Thanks Khaled
... View more
01-14-2019
08:54 AM
|
1
|
19
|
2806
|
|
POST
|
Can you pl. provide me with accessible link to the feature service. Will be good to have it as public if it is ok with you. The last link you sent me was inaccessible to me. Will take a look.
... View more
01-14-2019
07:30 AM
|
0
|
21
|
3631
|
|
POST
|
We do not have any currently known bug in the export to filegdb. Do you have a link to the service to look at?
... View more
01-11-2019
07:38 AM
|
0
|
24
|
3631
|
|
POST
|
Eric, Not sure if you have lots of data in the related table. But if you do, will be good to index the fkey in the related table. try this first: https://url/ArcGIS/rest/admin/services/<service2>/FeatureServer/<relatedTableId>/addToDefinition Pass the following json: { "indexes" : [ { "name" : "myindex", // some unique name "fields" : "<fkey name in the related table"> } ] } Will be good to have this in your related table. Without indexing the related table foreign key, will get slow query and you might timeout and the results might be flaky like what you see. Thanks Khaled
... View more
01-10-2019
04:25 PM
|
1
|
1
|
5457
|
|
POST
|
Yes there is a unique index on the objectid. We normally there are issues with ObjectId based relationships and we always recommend GlobalId based relationship. Once thing you can try is export this service to a filegdb and then add it as another service with a new name. The objectId based relationship will be converted to one based on GlobalId and it would preserve the original ObjectId. When you add a related record you will be using the GlobalId instead of the globalId. Khaled
... View more
01-10-2019
04:01 PM
|
0
|
26
|
3631
|
|
POST
|
One place to look is the foreign key value in related table. It should match a primary key in the source or origin layer. You need to be sure also to create a unique index in the origin layer. To create a unique index, you need to use the layer addToDefinition admin API. Origin layer: https://url/ArcGIS/rest/admin/services/<service2>/FeatureServer/<layerId>/addToDefinition Pass the following json: { "indexes" : [ { "name" : "myindex", // some unique name "fields" : "<primary field name in the origin", "isUnique" : true } ] } You might need to create the index and repeat the workflow again if you do not have a unique index already. By the way, you can create the unique index from the UX as well. So I would recommend: 1. Create the unique index on the origin layer primary key that you will be using for the relationship. 2. Add the relationship again. You might need to start from scratch (sorry). Hope that helps. Khaled
... View more
01-10-2019
03:42 PM
|
0
|
1
|
4261
|
|
POST
|
Yes this is doable as long as the view is created from the same parent service. The steps are: 1. Create an empty service using portal API with "isView" = true 2. Use the Feature service addToDefinition admin API to add a view layer based on the parent source feature service. You can add a definition expression in the layer metadata. The json used here can be something like: https://..../ArcGIS/rest/admin/services/<myViewSerivceName/FeatureServer/addToDefinition { "layers" : [ { "adminLayerInfo" : { "viewLayerDefinition" : { "sourceServiceName" : "<source service name>", "sourceLayerId" : <source layerId>, "sourceLayerFields" : "*" } }, "name" : "<name of the view layer", // Can be different from the source layer "displayField": "", "description": "", "copyrightText": "", "defaultVisibility" : true, "drawingInfo":{"renderer":{"type":"simple","symbol":{"type":"esriSFS","style":"esriSFSSolid","color":[76,129,205,191],"outline":{"type":"esriSLS","style":"esriSLSSolid","color":[0,0,0,255],"width":0.75}}},"transparency":0,"labelingInfo":null}, "allowGeometryUpdates" : true, "htmlPopupType" : "esriServerHTMLPopupTypeNone", "maxRecordCount" : 1000, "maxRecordCountFactor" : 1, "definitionQuery" : "Status = 'some name'" // your time definition expression. Note pl. use sql'92 date query } ] } You can add as many layers as you want to each view as long as you reference the same parent service. Note: You can also do the above using the UX by creating a view from the source that has all source layers and then drops what you do not need using feature service deleteFromDefinition. https://..../ArcGIS/rest/admin/services/<myViewSerivceName/FeatureServer/deleteFromToDefinition { "layers" : [ { "id": 2 // This is the layerId that you do not want in the view }, { "id" : 3" } ] } Hope that helps. Khaled Hassen Online feature service Lead
... View more
01-10-2019
09:19 AM
|
1
|
1
|
2745
|
| Title | Kudos | Posted |
|---|---|---|
| 5 | 07-01-2026 04:05 PM | |
| 2 | 07-01-2026 08:31 AM | |
| 1 | 02-01-2019 08:31 AM | |
| 1 | 01-10-2019 04:25 PM | |
| 1 | 11-20-2025 03:21 PM |
| Online Status |
Offline
|
| Date Last Visited |
Monday
|