topic Re: Cannot Edit Using Javascript API Sample in ArcGIS JavaScript Maps SDK Questions

Cannot Edit Using Javascript API Sample

junespina — Sun, 10 Feb 2013 09:57:07 GMT

Hi,

Our organization is trying to implement a simple web editing mapping application using the Javascript API sample on the ArcGIS Resource Center. This is what we did.
a. We Downloaded the application
b. Edited the snippet for defining the Center
c. Add our feature service layer published through our ArcGIS Server
d. We also downloaded the ASP.NET proxy page and modified it per instructions from the resource center.

we noticed that the sample works (Editing) only when it is not downloaded. But when we downloaded it, the editing feature seems to be disabled...

Any Ideas?

Thanks in advance...

Jun

Re: Cannot Edit Using Javascript API Sample

RahulMetangale1 — Mon, 11 Feb 2013 11:15:50 GMT

For editing feature services are required (available from ArcGIS Server 10.1) Does the url you are using for editing have "FeatureServer" word in it? for example:
http://sampleserver3.arcgisonline.com/ArcGIS/rest/services/Fire/Sheep/FeatureServer/0

If you are using feature service please use fiddler or firebug to track the request sent to the server.

Re: Cannot Edit Using Javascript API Sample

JohnGravois — Mon, 11 Feb 2013 14:50:02 GMT

Rahul/Jun,

Feature services have been available since 10.0, they were not added in 10.1. Please check "What's New" in REST for more information.

Jun,
are you certain you updated the line of code in the application which defines the location of your new proxy?
are you hosting your application over http?

i would recommend continuing to test with our sample service before substituting your own layers.

Re: Cannot Edit Using Javascript API Sample

junespina — Tue, 12 Feb 2013 00:23:51 GMT

Rahul/jgravois

first of all thank you for the response

Rahul,

Yes we are using a feature service for editing. it actually works fine with the out of the box ArcGIS Server Application.

jgravois

We made sure that the proxy URL points to the proxy page. We are not actually sure if we need to create a proxy page, but we did it anyway. We tried running the sample in our server as-is without changing any snippet. The Editing function does not work...

jun

Re: Cannot Edit Using Javascript API Sample

RahulMetangale1 — Tue, 12 Feb 2013 03:39:55 GMT

jgravois thanks for correction. That was a big typo from my side.

Jun,

Can you use fiddler and firebug to track the request sent to feature service. That will help narrow down the issue.

Screen shot would help.

Re: Cannot Edit Using Javascript API Sample

DianaBenedict — Tue, 12 Feb 2013 14:39:29 GMT

Jun

What version of SDE is your data stored that you are using for your feature services? At one point I was unable to edit feature services that pointed to data that was stored in ArcSDE 9.3.1 database. I do not know if this is a "feature" of ArcGIS 10.1 or if it has been addressed in the new SP release (didn't really address it since we were moving all databases over any way). In any case, my edits would not work until I pointed my feature services to data that was stored in ArcSDE 10.0 or greater.

Re: Cannot Edit Using Javascript API Sample

junespina — Tue, 12 Feb 2013 20:55:24 GMT

Rahoul

I haven't tried Firebug before so I'm not really sure if I'm doing the right thing. here is the snap shot of the result of the Firebug Inspection... please find attached image.

[ATTACH=CONFIG]21735[/ATTACH]

Diana

We are using SDE version 10

Thanks for the reply guys...

Jun

Re: Cannot Edit Using Javascript API Sample

junespina — Thu, 21 Feb 2013 01:20:09 GMT

Hello,

Its been days, since i've posted this thread, at our end we tried doing everything from step 1. unfortunately the edit function still doesn't work...and its getting to be a bit frustrating...

can i ask, is there anyone who actually used the Javascript API sample, particularly the edit function, that worked?

I hope the guys from ESRI from the javascript department would help...thanks

Jun

Re: Cannot Edit Using Javascript API Sample

AdrianMarsden — Thu, 21 Feb 2013 07:30:48 GMT

Yes - we use it fine - after creating a brand new Enterprise 10.1 database - that was what was holding me back. Ensure that the account you use in the MXD. Service has the required rights and that they are being passed through OK. Set AGS logging to debug and take a look at everything that may be relevant (you may see failed attempts to edit or bad logins) - if you are using MS SQL switch on all the logging tools there to see if there are any failed write attempts.

Sacrifice the relevant amount of small furry animals to the dark gods.

Good luck

ACM

Re: Cannot Edit Using Javascript API Sample

RahulMetangale1 — Fri, 10 Dec 2021 20:23:59 GMT

Jun,

I am suspecting that proxy file path is not correct or it is not configured properly.
1. How are you setting proxy path. I would suggest you give absolute path ex: http://<link to proxy.ashx/jsp>
2. To confirm if proxy is setup correctly you can try following link:

http://<path to proxy.ashx/jsp>?http://www.google.com

If you can see google page then you can be sure that proxy is setup correctly.

Rahul

Re: Cannot Edit Using Javascript API Sample

DianaBenedict — Thu, 21 Feb 2013 14:32:24 GMT

Hello,

Its been days, since i've posted this thread, at our end we tried doing everything from step 1. unfortunately the edit function still doesn't work...and its getting to be a bit frustrating...

can i ask, is there anyone who actually used the Javascript API sample, particularly the edit function, that worked?

I hope the guys from ESRI from the javascript department would help...thanks

Jun

Jun
I have been using the editing functionality with the Javascript API successfully. I am able to edit ArcSDE data from both 10.0 or 10.1. After SP1 was realeased, I have also been able to edit SDE Data that is stored in 9.3.1 (seems like they fixed that issue).

Below is a list of "todo" to make sure that your data is editable:
1) Make sure you can edit the SDE data from within the MXD that you use to publish your service. Editor --> start editing. Select a feature or two and make a minor change then save the edits and confirm you do not get any errors. If you do then more than likely you are encountering permission issues.
2) In ArcMap, verify that the data that you are editing all come from one SDE connection (keep note of this connection information). Essentially, you want to have 1 mxd/service that contains the data that you are editing (points to SDE). Do not add any reference data to this MXD. You will want 1 or more seperate MXDs for your "reference" data. To make things simple, I would only add 1 SDE layer in your "edit feature service" mxd.
3) IMPORTANT: In order to edit data via your feature service, you MUST Add a "Data Source" to you ArcGIS server. If you do not do this you will see an error when you attempt to "analyze" and publish your feature service. Use your ArcCatalog GIS Server connection to add a data source. This Data Source must match the SDE connection mentioned above. You can simply import the same connection information.
4) Verify the "Geodatabase Connection Properties" matches the "transactional version" that you are connecting to in your ArcMap MXD. (In ArcCatalog r-click the connection --> Geodatabase Connection Properties) verify against the MXD data source (TOC--> source tab) all of this should match up with the right version).
5) Publish the service: if all is done above correctly then you should get no Errors (maybe warnings).
6) Confirm your Proxy is working correctly. Use Firefox --> Firebug or Chrome (ctrl + shift+ i) to view the network traffic and errors OR IE9 F12 (refresh the page so you can see if all is well with your app)

Good Luck

Re: Cannot Edit Using Javascript API Sample

JoseSanchez — Wed, 19 Feb 2014 18:08:48 GMT

Diana,

When using SDE with JavaScript do you post/reconcile with JavaScript or open the version with ArcMap to post?

Thanks

Re: Cannot Edit Using Javascript API Sample

JeffPace — Wed, 19 Feb 2014 19:02:55 GMT

There is no post and reconcile in javascript. You are editing in the version posted (or version defined at 10.2) and its last in last out .

That version would then be reconciled back at the office, or you could publish a geoprocessing tool to do it