Latest Contributions by Arne_Gelfert

I'm currently in the process of converting some JSAPI 3.x code to 4.x. It used to be you could do this in 3.x    //Use esri/tasks/PrintParameters, esri/tasks/PrintTask //To get this var params = new PrintParameters(); var webMapAsJSON = printTask._getPrintDefinition(<currentMap>, params);   webMapAsJSON could then be sent to a custom geoprocessing service using   var gp = new Geoprocessor("your service's url")   and manipulated to your heart's delight in Python on the back end. Looks like "PrintTask" was deprecated back in 4.24... is there any way to still grab that JSON? I do not just want to send current state of web map to a layout using the new "print" module. I have all kinds of existing logic in arcpy that I  want to apply before creating a PDF.   ... View more

Anyone come across this lately?  ExecuteError: ERROR 001426: Failed to retrieve the job status from hosted services. Failed to execute (UploadServiceDefinition). I see  some older posts (2019) but nothing more recent. Just spun up a new test environment for Enterprise 11.3. Trying to get some services published in batch via arcpy using Pro 3.3. Seems to all be working but I still end up with this error. When I check, I see it successfully  created both an item in Portal and a service at REST endpoint for my federated server. So is this merely some timeout thing with status or something I need to investigate further? Weird thing is that the machine isn't actually configured as hosting machine as the error suggests.  ... View more

Simple question(s) alert !  (Although some of you may find it vague or missing more detailed code. Unfortunately, I cannot paste all my code here.) Why would hitTest() only return basemap hits as a result when I have several layers in my map? Do layers from a webmap brought into your app as Portal item work differently from those that are added as layers (Featurelayer/MapImageLayer) via URL? I recently started transitioning from JSAPI 3.x (WAB-DE stuff) to 4.x (4.30) and might be stuck in some legacy way of thinking. When I do this: view.on("click", (event)=> { view.hitTest(event).then((response) => { // Hoping for some results from the layers in the map // but response.results include only the basemap. console.log(response.results.length) // = 1 }); });   When I try with options, and specifically list one of the layers in the map, I get the same result. view.on("click", (event)=> { opts = { include: interesting_layer}; view.hitTest(event,opts).then((response) => { //Hoping for some results from the layers in the map; //But no! console.log(response.results.length) // still = 1 }); });   Where does interesting_layer come from? I currently loop through webmap layers once view has loaded and assign some names to key layers I want to interact with later. var interesting_layer; view.when(function() { //The following is another simplified version of what's actually //defined in another function elsewhere webmap.layers.forEach(lyr => { if (lyr.title == 'layer_of_interest') { interesting_layer = lyr } });    ... View more