POST
|
Interesting, I don't have the eyeball thing in my WAB. But if you are suggesting the attribute table tool to be enabled, I have already done so,as shown in the pic below.
... View more
06-14-2016
10:38 AM
|
0
|
4
|
612
|
POST
|
Daniel, I made the changes in the main WAB folder, so all the widgets I produce now will have the capability to move the pop-up right from start. I don't have to worry about making the changes each time I update or make a new widget.
... View more
06-14-2016
10:12 AM
|
0
|
1
|
1922
|
POST
|
Hi Adrian Welsh, I tried the same steps but the ' Open Attribute Table' button doesn't show up in the operational layer pull down menu. For that matter, the 'Open Attribute Table' does not appear in any of my attribute table. I have enabled 'query' capability for all my services.
... View more
06-14-2016
09:52 AM
|
0
|
6
|
612
|
DOC
|
Thanks for the reply Michael and Robert. It indeed was the record limit issue. For someone struggling with similar issue, here are the steps to increase the limit: Log into ArcGIS Server Manager and find the map service you are interested in. When you find the service, click on the pencil icon next to the service name which lets you edit the service details. When editing the service, click on the tab on the left which says "Parameters" and then there is a setting under properties called "Maximum number of records returned by server" - you should be able to change the value there. By default, the number is 1000. Select "Save and Restart" when done editing to save the saves and restart the service. Thanks, Shital
... View more
05-25-2016
03:59 PM
|
0
|
0
|
3241
|
DOC
|
Hi Robert Scheitlin, GISP, A colleague of mine encountered something interesting this morning while using the 'buffer' in enhanced search widget this morning that I wanted to bring your attention to. On using a small buffer radius like 0.2 mile from a point, we could select all the parcels in the proximity. But on using a buffer distance of 0.5 miles, the tool does not select all parcels within the radius. I haven't set any maximum buffer distance in the widget. Any thoughts on why this is happening? Again, thank you for your time in advance.
... View more
05-25-2016
10:40 AM
|
0
|
0
|
3241
|
POST
|
You might wanna try the solution posted by Tyler. It worked for me
... View more
05-25-2016
10:20 AM
|
0
|
3
|
1922
|
POST
|
This worked like a charm Tyler. Thank you so much. Much appreciated!
... View more
05-16-2016
12:09 PM
|
0
|
0
|
916
|
POST
|
Hi Tyler Dunn Thank you for posting this. Its super helpful for someone like me who has just started on js. I tried changing my code like you suggested and was only partially successful to replicate. I changed my 'common' file and was able to get the pointer changed into a move cursor. But upon making subsequent changes on the utils.js file, the WAB stopped displaying any map at all. I went back and took out all the new codes I added and it looks like the addition of function(Moveable, domClass) is creating some anomaly. I should also tell you that I couldn't find 'domClass' or 'dom-class' anywhere else in the code. Can you please tell if there is anything I am doing wrong? Thanks in advance. Shital
... View more
05-16-2016
10:51 AM
|
0
|
7
|
916
|
POST
|
These were reported as bug to ESRI: BUG-000094685 - Keyboard issue in Query widget in Samsung Galaxy 2. BUG-000094469 - Keyboard issue in Search widget on large Android tablets. Anyone feeling energetic enough can also try fix the problem themselves. Here is an excerpt of my conversation with ESRI to help folks get started: "I was able to test this issue in Microsoft Web Matrix until my free trial of Browser Stack ran out. I was able to isolate the issue to the 'jimu-ismobile' class in the jimu.css file. If you wish for the keyboard remain open you need to navigate to the ConfigManager.js file and replace the code in the _isRunInMobile function with "return true;". The root cause of the issue is that the Android keyboard appears when an input element comes into focus. However the Android keyboard causes the DOM to be redrawn, removing the focus from the input element. This causes the keyboard to immediately collapse..... If you wish to have a more permanent fix you will need to wait for the bug to be resolved."
... View more
05-10-2016
09:42 AM
|
0
|
2
|
584
|
POST
|
My web app created from Web Appbuilder works fine in smaller tablet. But I tried the same in a gigantic Samsung 18 inch android tablet (bought for my field crew) and it doesn't let me type in any text in the search widget. It seems the browser takes it as a desktop computer and takes off the on-screen keyboard after popping-up for fraction of second. Is there a way forward for me with big screen android tablet ?
... View more
04-21-2016
02:11 PM
|
0
|
4
|
2389
|
POST
|
Hi Hardolph, I have a similar but a different situation. I tried your suggestion, but the problem is mine is a sewer line and it has to go from a certain manhole(e.g. No 3372) to certain manhole (e.g. 3373). I have those data in the attribute table. With your solution, all of my sewer lines either go from left to right or from right to left. Is there a way to give them a flow direction based on altitude or from-to data ? Any help will be appreciated!
... View more
03-03-2016
02:34 PM
|
0
|
0
|
3406
|
DOC
|
Got it......Can't believe I missed this simple fix. May be because I was thinking hard all week to get the esearch widget to work. Thank you so much for your time!
... View more
02-26-2016
11:03 AM
|
0
|
0
|
3569
|
DOC
|
Robert, Yes, I have set up the symbology. As you can see in the two figures above, the upper search adheres to the symbology (for subdivision layer) and the lower (for parcel layer) doesn't!
... View more
02-26-2016
09:45 AM
|
0
|
0
|
3569
|
DOC
|
Thank you TAPAS DAS and Robert. So I talked to my IT department and they were quite skeptic on configuring proxy as a solution, mainly because all other widget (including identity widget) was working fine. So, as a final try, I reinstalled the esearch widget and tried it with the default search layer. Then I deleted them one by one and added my own search layer and voila it worked . The only thing that I did different this time was to replace the default geometry service with that of our own in the config.json. Thanks for the pdf Tapas. However, I am having a small problem after I got the widget to work. Of the two search layer that I am using, 'parcel' layer doesn't highlight the selected parcel. So by looking in the mapviewer it is difficult to tell what parcels did you exactly select (however you can identify the selected parcel by looking at the attribute table). But for the 'subdivision search layer' , the selected subdivisions are highlighted with bold reddish color. Does it have to do anything with the original coloring of the features in webmap? Or do I have to make some changes in the javascript to give a more dominant color thereby highlighting my selection? I am attaching two figures to explain my point. (The blue buffer on the second figure shows the selected parcels that are hard to identify) Thanks, Shital
... View more
02-26-2016
09:22 AM
|
0
|
0
|
3569
|
Title | Kudos | Posted |
---|---|---|
1 | 06-16-2016 09:27 AM | |
1 | 03-03-2017 11:50 AM | |
2 | 03-03-2017 11:47 AM | |
2 | 09-30-2016 11:31 AM |
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|