|
POST
|
Fantastic! I will say that the keyboard blocking the inputs is just one of the issues, the even bigger issue, in my opinion, is that the keyboard doesn't stay open. If you watch the video I attached, you'll see that I have to click into the inputs 2 to 3 times just to get the keyboard to stay open. It never stays open on the first click. It's extremely annoying.
... View more
03-05-2026
04:28 PM
|
1
|
0
|
1014
|
|
POST
|
Thanks for that suggestion @ColinLawrence but I don't really have time for all of that, and unfortunately, ESRI doesn't pay me to be a beta tester for them. But feel free to log it yourself if you want – I'm sure there’s going to be MANY more complaints about this because it's so bad and unusable. How this was able to get through ESRI’s “testing” is beyond me.
... View more
03-04-2026
11:17 AM
|
1
|
3
|
1131
|
|
POST
|
@ColinLawrence My iPad is running: iOS: v26.3 (however, other employees are on various 26.X versions) Field Maps: v26.1.0.2533 Here's a screen recording better showing these issues: How is it this bad? Maybe your developers need a Claude Code subscription so it can do it correctly for them the first time!
... View more
03-04-2026
10:27 AM
|
3
|
5
|
1157
|
|
POST
|
Updated to the latest Field Maps today, and now integer fields display this tiny numerical keyboard, but it's the worst user experience ever. When I click into an integer input, then the tiny keyboard will display for a second, but it seems like the large keyboard or the footer at the bottom tries to open too, and then they both just close. So, then I click into the input for a second time and sometimes the tiny keyboard will display fine, but other times no keyboard displays at all. So then I need to click into another input and back into it again! This is not a good user experience at all. The tiny keyboard makes filling out the form very difficult. It also covers the inputs way too much. You can't even see what you're entering. Is this by design? I sure hope not! Any idea how I can disable this tiny numerical keyboard for our users?
... View more
03-03-2026
03:29 PM
|
9
|
15
|
1660
|
|
POST
|
"The bugs we can report and many of them get fixed with the next update." I don't believe that for one second. That hasn't been my experience, or any other persons experience that I know. In fact, it's a meme online how terrible Esri is at doing bug fixes in a timely manner.
... View more
04-23-2025
07:42 AM
|
2
|
2
|
5087
|
|
POST
|
I've been using ArcMap for as long as I can because it actually works, but I know it's being retired next year. I figured Pro would have a lot of improvements since I last tried to use it, but it's exactly as I remember... a buggy, unusable mess. All I'm doing is dragging a field over to the end of the attribute table and it crashes every single time (video attached). Unbelievable... actually not at all, at this point I just expect it.
... View more
04-22-2025
06:00 PM
|
4
|
18
|
7590
|
|
POST
|
I found out what was wrong not too long after posting, but for some reason I couldn't find this post, so I thought it was deleted or something. Anyway, the problem is that featureLayer has been changed to just layer now. Once I made that change, then it worked. sources.push({
layer: new FeatureLayer({
url: 'OurServer/MapServer/2',
}),
name: 'Service Point',
displayField: 'gs_name',
outFields: ['*'],
searchFields: ['gs_name'],
placeholder: 'Search for customer information.',
maxResults: 3
});
... View more
03-08-2023
03:47 PM
|
2
|
0
|
981
|
|
POST
|
I keep just getting: No results There were no results found for "search term". When there should be results. I'm upgrading apps to 4.26, and the Search widget just isn't working. I even tried a very simple example, and it's still not working. 'esri/widgets/Search'
Search
// SEARCH WIDGET
const sources = [];
sources.push({
featureLayer: new FeatureLayer({
url: 'OurServer/MapServer/2',
}),
name: 'Service Point',
displayField: 'gs_name',
outFields: ['*'],
searchFields: ['gs_name'],
placeholder: 'Search for customer information.',
maxResults: 3
});
const searchWidget = new Search({
view: view,
sources: sources,
includeDefaultSources: false,
});
view.ui.add(searchWidget, {
position: 'top-left',
index: 0,
}); Super simple, but it just doesn't work. I don't see any network requests either. Any idea what could be wrong here?
... View more
03-07-2023
02:58 PM
|
0
|
2
|
1009
|
|
POST
|
Ooh great, I didn't realize that, I'll give it a try... thanks!
... View more
11-30-2022
05:14 PM
|
0
|
0
|
1406
|
|
POST
|
Is there an easy way to have the Expand widget show text instead of icons?
... View more
11-29-2022
02:57 PM
|
0
|
2
|
1466
|
|
POST
|
Sorry Rene, I figured it out after I posted... I tried to delete the post but it wouldn't let me. And now I can't get the original post back. I realized I had another layer where I was setting: layer.labelingInfo = null And that's what's throwing the error, where it worked in v4.21. It looks like I should be using labelsVisible instead.
... View more
11-16-2022
03:46 PM
|
1
|
0
|
1191
|
|
POST
|
11-16-2022
02:55 PM
|
0
|
2
|
1250
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 03-04-2026 11:18 AM | |
| 1 | 03-05-2026 04:28 PM | |
| 1 | 03-04-2026 11:17 AM | |
| 3 | 03-04-2026 10:27 AM | |
| 9 | 03-03-2026 03:29 PM |