Latest Contributions by JamesCrandall

One possibility is to simply set a variable so that you can use it to write the featureType to your output file: for fc in fcList:     desc = arcpy.Describe(fc)     featType = desc.featureType‍‍‍‍‍‍‍‍‍ ... View more

Looks like arcy.Describe() is what you will need.  http://pro.arcgis.com/en/pro-app/arcpy/functions/featureclass-properties.htm ... View more

Robert, My initial testing shows that your suggested changes to the WidgetManager.js file does in fact resolve the cache issue on the eSearch widget in Chrome Version 61.0.3163.100.  That is very generous to provide the solution and it's greatly appreciated. I'm not exactly sure how to proceed with this other than running thru a bunch of testing and then presenting those findings and potential solution to the management team here in our organization.  They'll need to decide if modifying an ESRI source component to all of our WAB products is acceptable or not.  If anything it will likely come back to me for a suggested path forward --- do you see any possibly way that the suggested changes could have negative affects? Again, your suggestions, solutions and interest in this issue is very much appreciated. ... View more

I'll implement asap!  Much appreciated. ... View more

Thank you! Also, adding the meta tags in the index.html had no effect.  The only way to see changes in Chrome is to clear cached images and file. <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate"> <meta http-equiv="Pragma" content="no-cache"> <meta http-equiv="Expires" content="0">‍‍‍‍‍‍ ... View more

Robert, I tested the scenario you specified above and I was able reproduce the caching issues in Chrome only.  IE did not cache the widget.  That is, reconfigurations of the eSearch widget that are redeployed would show the changes after a browser refresh.  However, in Chrome it required a clear of the cache in order to see those same changes. Are you implementing anything in the eSearch widget that attempts to deal with this? Thanks again! ... View more

I see.  Thank you for that bit of info and will try to replicate that! ... View more

Yes I see the change in the widget UI going from 1.3 to 2.5, then again back from 2.5 to 1.3.  I even did another round of this and at all tests the widget changed (ie. it did not appear to cache anything at all)! ... View more

Just to be sure. What you are saying is that with the no cache stuff in the index,html you did not see the change to the widget going from 1.3 to 2.5? Sorry Robert, I should have qualified my post with more info.  No, I did NOT alter any code or files -- just straight-up vanilla WAB apps that I added the eSearch widget to at their respective versions and then deployed each one during each test. WAB 1.3 has the eSearch widget at version 1.3.0.2 WAB 2.5 has the eSearch widget at version 2.5 ... View more

I did some testing and simply cannot reproduce the original issue. 1. Create duplicate WAB applications in WAB Dev 1.3 and 2.5 2. Deploy 1.3 version and verify EnhancedSearch widget functions at that version 3. Keep same IE 11 browser open, deploy 2.5 version to same location (url).  EnhancedSearch widget functions at that version. 4. Keep same IE 11 browser open, deploy 1.3 version again to same location (url).  EnhancedSearch widget functions at that version. I was expecting the browser to cache the widget at each version (there are obvious differences in functionality from 1.3 to 2.5) but they didn't appear. I replicated this same test method using the AdvancedDraw and regular ESRI Draw widgets, on multiple computers with different login/user accounts.  Basically the same results as above: upon a refresh of the browser (not a close/open/back_forward) the widgets would function as expected. ... View more

Aside from never allowing the browser to cache, what other potential affects (if any) would the following added to the index.html bring up? <meta http-equiv="Cache-Control" content="no-cache, no-store, must-revalidate"> <meta http-equiv="Pragma" content="no-cache"> <meta http-equiv="Expires" content="0">‍‍‍ ... View more

I second the request!  Even loosely thought out, unorganized and untested suggestions would be welcomed! ... View more

The big question is: why is this issue specific to WAB products? I could be incorrect in my understanding, but I don't know if our other enterprise apps (SAP, or any other business app) has to deal with cache problems anytime they rollout a new version to the same url. ... View more

I found that thread too but wasn't sure if these items at WAB Developer 1.2/1.3 were still contained in our current version of 2.5 --- I'll dig around to take a look. Thank you! ... View more