Closed MikeMillerGIS closed 7 years ago
@jessnoo is this still an issue?
I'm not sure where the 'Memory Issue' title came from, it looks to me like an issue with 2 different maps.
@SteveGrise updated the title
@MikeMillerGIS @SteveGrise Yes -- this is still an issue
in this example from the 1.4 testing, the input mapping file is for fGDB to eGDB -- but the oracle DB isn't updated -- and the messages indicate my previous test with a shapefile was used.
Code was only checking one map not all maps. Should always check all maps, also should not need to do that if the layer is selected and passed as a layer object. Addressed in fix for #86
validated with sprint 1 drop for dec 2016
Reported by @jessnoo
set up: fgdb1 - evacuationroute fgdb2 - evacuationroutetarget hosted fs - called evacuationroutetarget (eg http://services.arcgis.com/8KEQHzVdm3qDSW1h/arcgis/rest/services/EvacuationRouteTarget/FeatureServer/0 where the 0 layer name is EvacuationRouteTarget)
Map with fgdb1 evacuationroute and the hosted feature service loaded into it Another map with fgdb2 layer loaded in it and called evacuationroutetarget
Repro Steps: