So we pretty much have everything working (thanks to @Scott_Rawhouser and his guide to attaching photos) except for comments.
In our ParksFinder config.js file, on line 132 (the URL for CommentsLayer) if I use this URL:
http://<internalserver>:6080/<webadaptor>/rest/services/LGDM/Parks/MapServer/1
Then the map works splendidly up until I attempt to submit a comment. Where I get the following error:
"Unable to add comments. Comments table is either absent or does not have write access."
Which isn't true. Because if I then travel to the URL for the 'applyEdits' for that service...
http://<internalserver>:6080/<webadaptor>/rest/services/LGDM/Parks/FeatureServer/1/applyEdits
And I copy and paste the JSON from a failed attempt:
[{"attributes":{"FACILITYID":"Adm-29","COMMENTS":"Testing.","SUBMITDT":1409763555973,"RANK":0}}]
I get success=true and suddenly that park DOES have a comment.
But if I set the URL in my config.js file to be for a FeatureServer vs. MapServer then simply clicking on a Park (to bring up the popup InfoWindow) locks up my app with the spinning bar of death.
Any idea why I can post comments to a Park through the REST Services applyEdits URL but not through the application?!
Solved! Go to Solution.
Ok. Fixed it. Got it.
It all requires you to pick your URL's carefully.
For instance...
Our Internal (only) map is located on an internal server and referenced with:
http://<internalserver>.main.cityoftulsa.org/ParksFinder
The services were being referenced via the direct:
http://<internalserver>:6080/<web adaptor>/rest/services/blah blah blah
So I was using that URL in the Operational Data Layers. And everything was working fine (excluding the comments).
We noticed that I was able to go to that URL ( http://<internalserver>:6080/<web adaptor>/rest/services/blah ) and add in /applyEdits then copy and paste the JSON code (from a failed post attempt) into the adds textfield and voila! It created a comment.
But the app couldn't.
So I found the fully formed URL for the ParksFinder app... modified it to get the rest services the same way the app was referencing them... http://<internalserver>.main.cityoftulsa.org:6080/<web adaptor>/rest/services/blah and voila.
Everything now works.
Ok. Fixed it. Got it.
It all requires you to pick your URL's carefully.
For instance...
Our Internal (only) map is located on an internal server and referenced with:
http://<internalserver>.main.cityoftulsa.org/ParksFinder
The services were being referenced via the direct:
http://<internalserver>:6080/<web adaptor>/rest/services/blah blah blah
So I was using that URL in the Operational Data Layers. And everything was working fine (excluding the comments).
We noticed that I was able to go to that URL ( http://<internalserver>:6080/<web adaptor>/rest/services/blah ) and add in /applyEdits then copy and paste the JSON code (from a failed post attempt) into the adds textfield and voila! It created a comment.
But the app couldn't.
So I found the fully formed URL for the ParksFinder app... modified it to get the rest services the same way the app was referencing them... http://<internalserver>.main.cityoftulsa.org:6080/<web adaptor>/rest/services/blah and voila.
Everything now works.
another very good way to implement the parks finder and all the web mapping templates is to use cartoview to integrate your apps in one site. The samples cartoview demo is actually powered by the feature service from Cartoview rather than ArcGIS Server