Latest Contributions by MattNicol

I had a similar issue where I got an error message about an invalid invocation of the constructor for my WPF user control. I got around this by adding an empty ElementHost to my WinForm and then adding the control through code:         public Form1()         {             InitializeComponent();             elementHost1.Child = new MyWPFUserControlLibrary.UserControl1();         } ... View more

Ganesh, It's a little tricky to post my code here without posting some sensitive data, but basically, I do get the Create Drive Time Areas widget to render with no visible errors.  However, when I click "Show Credits" or "Run Analysis," the container the widget is housed in scrolls up instead of running.  I'm assuming it's trying to highlight some sort of client validation error, but nothing is shown.   I can give you more details privately if needed, but a snippet of my code to initialize the widget is below.  I am using the 3.23 version of the API that's configured automatically through a downloaded WebApp Builder application that I'm writing my own custom widget for.                 var fl = new FeatureLayer(myFeatureLayer.url, { opacity: 0.5 });                 fl.name = "My Layer";                            var cdtaOpts = {                     inputLayer: fl, ,                     inputLayers: [fl],                     inputType: "point",                     map: myMap,                     portalUrl: "https://myurl.maps.arcgis.com",                     showCredits: true,                     showSelectAnalysisLayer: true,                     showReadyToUseLayers: false,                     showChooseExtent: false                 };                 var cdta = new CreateDriveTimeAreas(cdtaOpts, "createDriveTimeContainer");                 cdta.startup(); ... View more

I posted this here too: https://community.esri.com/message/678700-getting-a-stringsubstitute-could-not-find-key-layername-in-template-error-when-trying-to-initalize-createdrivetimeareas If you add a "name" property to your input layer, you'll work around there.  In the CreateDriveTimeAreas code, "layername" is set to your inputLayer.name.  Layers from ArcGIS Online have this.  Layers created from instantiating your own FeatureLayer do not.   Basically, add:   activeFeatureLayer.name = "Some name";   Unfortunately, in my own case, I still could not get CreateDriveTimeAreas to work, but the step above did get rid of that "layername" error message for me. ... View more

If you add a "name" property to your input layer, you'll work around there.  In the CreateDriveTimeAreas code, "layername" is set to your inputLayer.name.  Layers from ArcGIS Online have this.  Layers created from instantiating your own FeatureLayer do not. Basically, add: myLayer.name = "Some name"; Unfortunately, in my own case, I still could not get CreateDriveTimeAreas to work, but the step above did get rid of that "layername" error message for me. ... View more

I've made progress on this and will leave it here in case it helps anyone else. If you do not have proxy rules in place in your Web AppBuilder config.json file and the proxy's proxy.config to the URL to the underlying Web map, the user will be presented with an ArcGIS.com login prompt upon arriving at your site. ... View more

I didn't log this with Esri support, but I'm guessing it's related to the format of the query that the ODBC driver is expecting.  In SQL Server Management Studio, for instance, you can issue the query in the form that's set in ArcMap by default, and it will run successfully.  (SELECT * FROM <database>.<schema>.<table>)  So I would think that either ArcMap is transforming the query somehow before sending it or the ODBC driver is somehow mishandling the query in such a way that removing the database qualifier fixes it. ... View more

Robert, That's perfect - thanks! ... View more

I just ran into this in 10.5.  I put more detailed instructions here: https://community.esri.com/thread/189576-there-is-an-error-during-the-draw-layer-name1-dbms-table-not-found42s02microsoftodbc-driver-11-for-sql-serversql-serverinvalid-object-name-db-name2-service-account3-viewtable4 To summarize though, remove the database name from the query in your layer in ArcMap. Layer Properties > Source > Change Query In my case, the query was:  select <columns> from <database>.<schema>.<table> Removing the <database> qualifier resolved it. ... View more

I ran into this in 10.5.  Here's how I resolved it: In ArcMap: Layer properties > Source tab > Change Query The query was in the form of "select <columns> from <database>.<schema>.<table>". I removed the <database> qualifier, and after saving the map document and overwriting the map service, the features correctly displayed in the preview in ArcGIS Server Manager and in my Web application. So, change the query in ArcMap to this: select <columns> from <schema>.<table> ... View more

Print requests do not include the Bing Maps key for some reason.  If you're using a proxy to handle requests, you can add the Bing Maps key through code, and the request will authorize. Look for something like this in your request: [{"id":"layer2","visibility":true,"type":"BingMapsroad","culture":"en-US","opacity":1} And change it to this: [{"id":"layer2","visibility":true,"token","<YOURBINGMAPSKEY>","type":"BingMapsroad","culture":"en-US","opacity":1} ... View more

Curtis, thank you for the idea!  My scripts were all running in-process. Surprisingly, in my empty script tool case, the tool finished in around 12 seconds when I ran it out-of-process.  When I tried this with my real script, I encountered an error though.  From the page below, it looks like Esri only recommends running scripts out-of-process in special cases: http://resources.arcgis.com/en/help/main/10.1/index.html#//00150000000r000000 ... View more

Thank you for the suggestions!  Unfortunately, they did not have an effect on performance in this case, but they all look like great suggestions for managing performance in general. ... View more