Latest Contributions by SteveCole

I've been developing under the 2.8 API and my app has loaded immediately but, under the 3.3 API, it's exhibiting a weird lag time. One of my featureLayers is constructed on the fly using a FeatureCollection. Using some well placed console.log commands, I can see that the code is, in fact, running immediately (including processing the deferred results which are used to construct the featureCollection). The problem is that those features are NOT visible or clickable for another 4 minutes! After that 4 minutes, the features suddenly appear and everything is fine. There's no error to speak of in the console and, again, it runs fine in v2.8 We're using ArcGIS Server 10.1. This app is currently running on an internal, developmental server but I'm hoping to push a public version soon (I have some other issues I need help with). Has anyone else experienced weirdness like this with the 3.3 API? Steve ... View more

This issue is driving me CRAZY and I'm at a lost to explain it, let alone know how to correct it. I'm developing a web map which will report back stream gage heights. That data is stored natively in an Access database but I have a python script which does a bulk extract every 5 minutes and then transfers the records into a standalone table in SDE. The data has an Epoch timestamp so I can confirm that the data inside the standalone table is current. One of the map requirements was that the gages on our map were symbolized by color based on their current flood stage. To facilitate this, I build the layer on the fly as a FeatureLayer using a FeatureCollection whose source is the standalone table previously mentioned. Last bit of context is that the standalone table is a layer tucked within a published map service with two other point datasets. My system was working fine when we still were running ArcGIS Server 10 but since we upgraded to 10.1, my mapped information is stale. At first, I thought the issue might be that the standalone table consistently has over 2,000 records and the map service had a MaxRecordCount of 1,000. We bumped that up to 5,000 for the map service but the individual layer still shows a MaxRecordCount of 1,000 when viewing its properties in the REST services directory. Through some testing, I think I can say that this is not the problem. I performed a query using "1=1" and it returned the 2,000+ records. So I'm left with a situation where my data is just "stale." I'm not responsible for the installation/maintenance of our ArcGIS Server but the person who is told me that one of the changes from 10 to 10.1 is that Server now pulls data locally onto the server. I'm starting to wonder if my app just keeps pointing back to a cached copy of the table's records?? My app has briefly worked twice under 10.1 and both times were immediately after deleting and re-adding the map service that includes the table. This behavior is what leads me to think that I'm a victim of cached data. How can I remedy this??? The app is still in development and not on the public side of our firewall, unfortunately. Steve ... View more

Trying to utilize the TableDataSource but I have no clue what the WorkspaceID is and where it can be found. The help docs don't have much to say about it. I'm trying to access a standalone table located in v10 SDE. Is it simply the name of the SDE database?? Thanks- Steve ... View more