nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Edits to SDE feature class not showing in jsapi site

JustinAnderson

Hello,

I have several SDE versioned feature classes that will be edited using different clients (ArcMap and a third party mobile application). This data
is accessed throughout the organization using an AGS JSAPI site we have developed. This site is built using dynamic map services and feature map services, but
no cached map services. When our operational layers are edited, the changes (adds, deletes) don't appear on our AGS JSAPI site upon its intial load. So, for example,
when the site intially renders a map, a feature that has been deleted outside the application is still visible. However, on any extent change (zoom in/out, pan, etc) the
edited data is rendered correctly (deleted features no longer visible). Refreshing the site in internet explorer, even many hours after the edits were written to the database has no effect (for the intial extent). I've tried restarting the map services with no luck. In addition, I've looked at the map service through the generic JSAPI viewer in the AGS services rest folder, with the same issue (initial extent problemtic, all other extents fine).

If anybody has run into a similar issue and can shed some light I would be very grateful.

Thanks,
Justin

Encontre mais publicações marcadas com

Accepted answers

All comments

derekswingley1

Are all apps referencing the same geodatabase version?

JustinAnderson

All applications are working with the same geodatabase version.

derekswingley1

In IE, does reloading with shift + f5 cause the feature to display?

JustinAnderson

Derek - Thanks for the suggestion. Unfortunately shift - f5 has no effect.

JeffPace1

IE is terrible isn't it?

It sounds like, since the initial load is always an identical request, IE is seeing this and caching the return map. When you navigate a new request is created and that is why it updates.

You can try a couple things to get around this.

1. Randomize you initial extent a few millimeters. User will never notice, but the requests will be unique (terrible but functional)
2. Check you reverse-proxy/web cache/firewall and set the particular service not to cache.
3. Even worse, if all else fails, you could add an dojo.isIE (do some tiny navigate)

sorry I can't think of better solutions. In fiddler, you should see if the initial map request is drawing new or displaying a cached result. This would confirm the behavior at least.

JustinAnderson

ESRI Support offered some good suggestions that fixed my issue. I just needed to add

.setDisableClientCaching(true);
and
.refresh();

to my dynamic map service and everthing works great.

Thanks,
Justin

AdrianMarsden

So, is refresh() an undocumented method of ArcGISDynamicMapServiceLayer? it certainly seems to do what it says?

AndyBurns

We have been using refresh since 2.8, i have to be honest though and say i have no idea (or cannot remember) how i stumbled across it.

 function refreshTimer()
  {
   setInterval(function(){
    dojo.forEach(electionLayers, function(layer){
     layer.refresh()
    });
   }, 30000);
  }

We have a call to refresh the dymanic service looking at SDE data, seems to work fine so far in all browsers.

Participe da Conversa

Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.

Links Rápidos

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.