Latest Contributions by DAVIDDAS1

Hi Robert, You have once again done an absolutely amazing job with version 1.2 of your Enhanced Search Widget. The integration with the Attribute Table now works like a dream. Moxie and his team did a complete overhaul of the Attribute Table in version 1.2 of the Web AppBuilder. It is now rock solid. The original issue with the spinning busy cursor and erratic load times have been fully addressed in this release. This makes it a joy to use your Enhanced Search Widget in WAB 1.2 I tested your Widget on six different themes. Foldable Theme: http://www.tapasdas.com/Maps/Phones/app41 I like how the Attribute Table now opens up and populates the selected records immediately. There is no lag. The foldable theme is ideal for viewing on Tablets and Smartphones. The GUI collapses gracefully as you reduce the size of the window. I came across one minor issue. I want to display a numeric field with 0 decimal places. However, in the results pane and popup it shows up with 2 decimal places. When I attempt to edit the Field Format, I see that the Precision option is grayed out. It is setting a default precision of 2 decimals places that I cannot change from the GUI. These are the map services I am using. Schools: http://gis.maricopa.gov/arcgis/rest/services/WAB/Schools/MapServer/0 Zipcodes: http://gis.maricopa.gov/arcgis/rest/services/WAB/Zipcodes/MapServer/0 Places: http://gis.maricopa.gov/arcgis/rest/services/WAB/Places/MapServer/0 County: http://gis.maricopa.gov/arcgis/rest/services/WAB/County/MapServer/0 Here is the ZIP file of this Web App which you can import in WAB 1.2 to test this behavior right away. http://www.tapasdas.com/Maps/Phones/app41.zip Launchpad Theme: http://www.tapasdas.com/Maps/Phones/app42 The Launchpad Theme is ideal for Laptops & Desktops. It allows you to have multiple widgets open at the same time. You can resize and move the widgets. You can minimize the open widgets to reduce screen clutter. It only takes one click of a mouse to convert the Foldable Theme to the Launchpad Theme. We will be publishing both versions, one optimized for Smartphones, and the other optimized for the Desktop. The Launchpad Theme gets closest to mimicking the Flex apps. However, I found a minor issue with the Launchpad Theme. I expected the Attribute Table to open the moment I got back the Search Results. It did not open automatically. As a workaround, I had to open the Layer List Widget and select Open Attribute Table. Then the Attribute Table showed up. This behavior is peculiar to just this theme. It works fine on the other themes. Dart Theme: http://www.tapasdas.com/Maps/Phones/app43 The Enhanced Search Widget GUI looks very stylish in the Dart Theme. However the Results Pane can be hard to read. This theme would need some CSS tweaks. Tab Theme: http://www.tapasdas.com/Maps/Phones/app44 The Tab Label "By Attribute" is too long. It does not fit. I would be replacing this with "By Text" or "By Data" in the \widgets\eSearch\nls\strings.js file. Box Theme: http://www.tapasdas.com/Maps/Phones/app45 I like how the Enhanced Search GUI is simplified when there is just 1 search expression. This gives it a cleaner look. Jewelry Box Theme: http://www.tapasdas.com/Maps/Phones/app46 Everything is working beautifully. You have made a solid release in record breaking time! Thanks a million!! ... View more

Hi Robert! Thanks a million for uploading your Enhanced Search Widget 1.2 (Version 33). ... View more

Hi Robert, That sounds perfectly ok! We all know you are working around the clock. I like the changes that were made to the Attribute Table. It works a lot better now. I do not get that annoying spinning icon any more. Thanks so much for the updates... ... View more

Hi Robert, I wanted to see how your Custom Widgets would fit into the new Themes available in the Developer Edition 1.2 of the Web AppBuilder. Moxie Zhang and his team have done a fabulous job introducing some new snazzy themes, styles and widgets. I was pleasantly surprised to find that your Enhanced Basemap Gallery widget works fine in WAB 1.2 without any modifications. However, your Enhanced Search Widget 1.1.11, Identify Widget 1.1.2, and Google Street View Widget 1.1.0.2 will need some extra tweaks. I have set up 6 test web apps for the 6 themes. I will test your WAB 1.2 versions of your Custom Widgets whenever you have them ready. Here are the web apps to test the behavior of the Themes. 1. Foldable Theme: http://www.tapasdas.com/Maps/Phones/app35 2. Launchpad Theme: http://www.tapasdas.com/Maps/Phones/app36 This lets you open multiple widgets, and move, resize, and minimize them like the Flex version. I like this a lot. Now we are getting close to the Flex functionality! 3. Dart Theme: http://www.tapasdas.com/Maps/Phones/app37 Just like the previous case, you can have multiple widgets open and move them around. 4. Tab Theme: http://www.tapasdas.com/Maps/Phones/app38 5. Box Theme: http://www.tapasdas.com/Maps/Phones/app39 6. Jewelry Box Theme: http://www.tapasdas.com/Maps/Phones/app40 A panel on the left is supposed to fly open. I haven't figured out how this works. The Attribute Table Widget feels more responsive and robust in version 1.2 There are some new eye-catching Style Colors. The Web AppBuilder along with your awesome Custom Widgets is making it possible for us to develop and deploy polished web apps in a matter of hours without writing a single line of code. This software has exceeded all our expectations. ... View more

Hi Gerald, I followed these steps while upgrading Robert's eSearch Widget from version 1.1.9 to 1.1.10 1. Replace the eSearch folder in client\stemapp\widgets with version 1.1.10 of the eSearch folder. 2. Launch the Web AppBuilder. 3. Duplicate the existing app into a new App. 4. Edit the new App. All my configurations were preserved. I got to access the new functions of the eSearch widget in version 1.1.10 Thanks, Tapas ... View more

Congratulations Robert!!! Jack recognized your contribution to ESRI's Online Community by awarding you the GeoNet Launch Champions Award at the Closing Ceremony today at the 2015 ESRI User Conference. All the Directors were on stage along with Jack. Your invaluable work with the Custom Widgets for the Web AppBuilder along with the Customization Resource List maintained by Rebecca Strauch were mentioned by Derek Law at the Web AppBuilder Technical Sessions. On behalf on the Web AppBuilder Community, I would like to say a million thanks to you and Rebecca. What you do is a work of passion. ... View more

Thanks Robert!! I would be looking forward to testing your next version. Thanks Kevin for letting me know that you got the eSearch working after a fresh install. ... View more

Hi Robert, We got another tip from ESRI that may explain why we are getting this error. Uncaught TypeError: Cannot read property 'geometry' of undefined They explained that the zoomall function is getting invoked before the queries are coming back from the server. The setTimeout value in milliseconds is there to delay the calling of the zoomall function allowing sufficient time for the results to be returned. Line 1574 on file widgets\eSearch\Widgets.js The default value was 300 milliseconds. This delay is enough for most scenarios. However, we are making searches on the Parcels Layer with around 1.6 million records. It can take around 12 seconds for the results to appear. So until this 12 seconds have elapsed, the array this.currentLayerAdded.graphics is empty. Line 1280 on file widgets\eSearch\Widgets.js So when the zoomall function tries to read the first item of this empty array, it throws the error. The trick will be to add the necessary logic to make the call to the zoomall function to wait until the array is populated. If the wait time is based on a fixed delay value like 300 or 600 milliseconds, it will be a hit and miss scenario. One cannot anticipate the size of the database being queried. This makes the solution complex. Perhaps the delay time can be a user defined value tied to a specific layer. Perhaps there could be a way to check to see if the array is empty before calling the zoomall function. Thanks, Tapas ... View more

Robert, That sounds great! I appreciate all your enhancements and new features. ... View more

Hi Robert, I have a simple enhancement request that will solve our problem with the Attribute Table right away. The real reason we like to have the results displayed in the Attribute Table is because of the nifty Export to CSV option. This is a powerful feature.  It allows us to view the results in Excel, make charts, reports, and perform further analysis. The Attribute Table also allows us an easy way to sort the columns. However, this can be done easily in Excel. So if the Export to CSV function is the only real requirement, would it be possible to add this option directly on your Results Pane? Here is a mockup of how it may look like: If we can get this option on the Results Pane, and the Export to CSV captures all the fields that are shown in the Popup, then we won't have any need to display the Attribute Table. We can completely bypass the Attribute Table, and enjoy faster performance, and more screen real estate to display the map. It would also be wonderful to have this Export to CSV option on your Identify Results Panel as well. In the Flex version of your Identify Widget, you had a Copy to Clipboard option which we found very useful. http://www.tapasdas.com/Maps/Desktops/web37 If you could give us an Export to CSV option on the Results Panel of your eSearch and Identify Widgets, it will immediately solve our issues. Thanks, Tapas ... View more

Hi Robert, We received a tip from ESRI to replace the LIKE operator with the "=" operator to improve response times with the Attribute Table. I made another test case = app34 I also changed the setTimeout value from 300 to 2400 as a test in the eSearch\Widget.js file on line 1574 I opened Chrome and cleared my browser cache with <Shift><Ctrl><Del> I launched app34 in Chrome: http://www.tapasdas.com/Maps/Phones/app34 The Search Layer = Parcels, uses the "=" operator. I opened the Console Window in Chrome Developer Tools. There are no errors at this point. I ran the example Search: APN = 16916033A The correct result appears in the Results Panel very quickly. Next, an empty Attribute Table appears with the spinning wheel. Next, the error message appears in the Console Window. Finally, the correct attributes are displayed in the Attribute Table. Note: If I rerun the exact same search a second time without emptying the cache, no errors are returned. If I run a new search with another APN value for example: APN = 16916033B APN = 16916034 the error comes back. Conclusion: Increasing the setTimeout value or replacing the LIKE operator with the = Operator did not help to remove the Error Message: Uncaught TypeError: Cannot read property 'geometry' of undefined ... View more

Hi Robert, Thanks for your super fast response as always! I tried your change on widgets\eSearch\Widget.js I cleared my browser cache with <shift><ctrl><del> in Chrome and reloaded app33: http://www.TapasDas.com/Maps/Phones/app33 When I ran the Attribute Search for Parcels, I still got the same error message in the Console Window for Developer Tools. Note: If I do not clear my browser cache, and reload the page a second time, and run the exact same attribute search, the error message does not come up. However, running a new Attribute Search like Parcel Number = 1691603 will again trigger the error message. Thanks, Tapas ... View more

Hi Robert, I would like to revisit the error message reported by Tim Jacobsen a few days back. This is not an issue with your Enhanced Search Widget 1.1.9, but rather with the Attribute Table Widget from the Web AppBuilder Developer Edition 1.1 that your Widget connects to. Nevertheless, I would like to bring this up because this is going to affect everyone of us using your Enhanced Search Widget. The problem is easily reproducible 100% of the time. To illustrate the issue, I have made 2 test cases - app32, and app33. The first one works flawlessly while the second one throws an error. Case-1: Enhanced Search Widget 1.1.9 without the Attribute Table. This one works perfectly fine all the time. Open app32 http://www.tapasdas.com/Maps/Phones/app32 Open the Enhanced Search Widget and search for the example Parcel Number = 16916033A The correct attributes are listed in the Results Pane. Next, try a search by Owner Name Enter the example Owner Name (Last Name, First Name) = Smith John 112 matches are returned Next, try a search by Address Enter the example Street Name = Dynamite 233 matches are found Everything works flawlessly under Internet Explorer 10, 11, Chrome, Firefox, and Safari. Now let's examine Case-2: Enhanced Search Widget 1.1.9 + Attribute Table. The only difference is that I have enabled these two options: Add Result as Operational Layer Show in Attribute Table Widget To reproduce the error, you must use Chrome as your browser. First you would need to clear our your Browser Cache by entering <Shift><Ctrl><Del> Next, launch app33 in Chrome: http://www.tapasdas.com/Maps/Phones/app33 Turn on Developer Tools in Chrome. There are no errors to start with. Search for the example Parcel Number = 16916033A The Attribute Table opens with the Busy Cursor After an annoyingly long wait, the Attribute Table does get populated. However, the Console Window in Developer Tools throws this error: Uncaught TypeError: Cannot read property 'geometry' of undefined These are the details: It appears this is something that Moxie and this team needs to address. Try a Search for Owner Name containing "Smith John" Once again you get the busy cursor, and after a long wait the Attribute Table gets populated. However, you get the exact same error message: Uncaught TypeError: Cannot read property 'geometry' of undefined You can ignore these errors. The app does work, albeit with a slow response time. Now here is the curious part. You can perform as many Graphical Searches you like. There are no errors! Also, the Attribute Table gets populated almost instantly during a Graphical Search. There is no lag. Robert, I know that you did not design the Attribute Table Widget. Your Enhanced Search Widget is simply displaying the Search Results through the built-in Attribute Table Widget in the Web AppBuilder. The Attribute Table Widget is the weakest link in the Web AppBuilder. I wish someone would recreate the awesome Data Grid you had in your Flex version of the Enhanced Search Widget. Thanks, Tapas ... View more

Kevin, Here is one thing you can try. Remove the eSearch Widget, and then add the eSearch Widget back into your Web AppBuilder session. This will essentially blank out the contents of the eSearch config file, and you will be starting fresh. When you add the URL to your 2015 Parcel Map Service, make sure that you include the index number at the end of the string. It must always point to a specific layer ID for it to work. For example, this will work: http://gis.maricopa.gov/arcgis/rest/services/PlanNet/Basemap/MapServer/1 However, if you leave out the layer index, it will not work: http://gis.maricopa.gov/arcgis/rest/services/PlanNet/Basemap/MapServer Thanks, Tapas ... View more

Hi Kevin, This should be fairly easy to track down. Could you please give us a copy of your config file for your eSearch? Could you also give us an Item List of your Web Map on ArcGIS Online that lists all the data layers you are using. It should be easy to match them up. Thanks, Tapas ... View more