Latest Contributions by davetinkle

nope. you might have better luck on reddit. seriously. ... View more

ok, but that has nothing to do with the bug you posted. please respond to my specific question, so i can understand what you're trying to state. thanks. ... View more

I have tried multiple times for multiple days to visit your link to the bug, but it will not resolve. Has this been rescinded or promoted? Can you confirm similar behavior when you click the link? Thanks. ... View more

Thanks Noah. I have to make adjustments to add a graphic to my MapView, and not add it to a FeatureLayer [and in turn add to Map] ... View more

Hi Noah, Would you mind doing something similar for the version i'm currently using -- stated as 4.14 in the thread title? Thanks. ... View more

[replied to email that assured me it would be posted here, but it did not, so i'm posting directly now w/ my emailed response from yesterday] --------------------------------------------------- Hi Noah,   Using a FeatureLayer. Here’s the simple fn I wrote that first revealed the issue [not drop-in ready, but close enough]:     function printSubmit():       require(["esri/tasks/PrintTask", "esri/tasks/support/PrintTemplate","esri/tasks/support/PrintParameters", "esri/tasks/support/LegendLayer"],     function(PrintTask, PrintTemplate, PrintParameters, LegendLayer) {                   disableButton('downloadButton','disableSubmitButton','canAddMapToCad','canAddToCad');     showDownloadProgressBar();            var pt = new PrintTask({         url: printTaskUrl     });     var template = new PrintTemplate();                          var d = new Date();     var mm = d.getMonth() + 1; if (mm < 10) mm = '0' + mm;     var dd = d.getDate(); if (dd < 10) dd = '0' + dd;     var yyyy = d.getFullYear();         var legendLayers = [];     // for now, do not show legend, as there's a known bug where 'Override 1' is displayed, instead of layer id/store type description     // ref: https://community.esri.com/thread/170974 & https://community.esri.com/thread/101287     map.allLayers.forEach(function(item, i) {        if (item.declaredClass == "esri.layers.FeatureLayer") {              var l = new LegendLayer({                 layerId: item.id,                 title: " "              });              legendLayers.push(l);         }     })     template.layoutOptions = {            titleText: mapTitle,            authorText: "ALERT Report Generated: " + mm + "/" + dd + "/" + yyyy,            copyrightText: "SBU - Sensitive But Unclassified",            legendLayers: legendLayers     };     template.format = "png32";     template.exportOptions = {         width: $("#mapDiv").width(),         height: $("#mapDiv").height()     };                          var pp = new PrintParameters();     pp.view = view;     pp.template = template;     pt.execute(pp).then(printComplete, printError);        })}   Hope this helps in your investigation. We’re still obliged to provide this service, so the ticket’s still valid. There is no workaround to the best of my knowledge.   Thanks. ... View more

Tanu, I delayed my response because I was assured this would be fixed in the next API release [how an unrelated Print service is related to an API release is still unclear to me]. I never used a FeatureCollection. I have always used FeatureLayer. To date, it still is NOT fixed, and does NOT appear to be correlated to the javascript API version, currently 4.11. I am using 4.6. Please explain both [1] why it isn't fixed, and feel free to correct me if it is [2] if there is a work around so when I print [using the print task, NOT the print widget], my legend also prints. The end resultant PNG/PDF **must, must, must** have the legend on the final product. Thanks. ... View more

Unfortunately, our code has branched too many times to retrieve what was causing it to fail. It would be very disruptive to revert, compile, deploy, trap packets & put it here. Don’t have a ticket number, but do have Case #02114883 & bug #BUG-000114062 Do you ask b/c you are part of the development team? ... View more

using JS API, and have upgraded every time in the hope someone would have fixed this. So that would make it 4.8 version. It's a known bug. I have a ticket. I don't know anything about GDI. All I know is I followed the API & printing a legend for a PDF is advertised as part of its core functionality, but it simply does not work. Thanks. ... View more

Tanu, Can you please provide a clear demonstration why you believe this is fixed? I used the sample server url as suggested, but as you can see in my attachment, it is not working. Do you - or anyone else subscribed to this thread - know of a way to use the print service & get intended, bug-free results? Simply put, displaying "Override 1" is unacceptable, and no one appears to be motivated to explain what's gone wrong, and when it's going to be fixed. I have submitted my code to the support developers, and they have been able to reproduce my error, and did not have a work-around or advice if my coding was incorrect. looking forward to your reply on my 2 questions. Thanks. ... View more

many months later, i now have a ticket/bug number: BUG-000114062 it's worth pointing out this has been a bug for half a decade! again I ask: does *anyone* here have a work-around? ... View more

Hi Alan, I'm choosing to reply here instead of PM in case others have happen to them what has now happened to me - my case got deleted! My customer number is XXXXXXXXXX, but I do not believe I used that for my ticket. If you believe the customer number to be sensitive info, please advise & i'll edit this post to remove it. I went to "Manage my Cases" and although it had a link to it, the content is no longer accessible, as if I've been "ghosted". I see there was a case opened quite a while ago relating to my issue: https://support.esri.com/bugs/nimbus/RU5ILTAwMDEwMzEyMw== [Bug ENH-000103123] Do you think we need to start from scratch? I'm not sure how to move forward with the cutoff in communication. Thanks, Dave ... View more

Hi Kelly, I promptly opened a ticket, and I have not yet so much as even been acknowledged by a human. To re-cap, in January 2018, you stated, "This issue is being actively worked on with the 10.6 print service", and in March 2018, you stated, "Some workarounds have been implemented in map viewer to overcome these issues for the time being, but won't be applied until the print service is upgraded. This is tentatively scheduled for the upcoming release of ArcGIS Online scheduled for April 10. " We're getting pressure from our user community to have this fixed ASAP, but what we're getting from the ESRI side is broken promises & crickets. Please reply back here very shortly with a timeline of when this will be fixed. If there is a work-around in the interim, please clearly convey that here on this thread, and not through private message or email or some other manner that will only benefit me, and not the community. Thanks, Dave ... View more