Latest Contributions by _____

‎04-23-2025

"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.

‎04-23-2025

I'm definitely blaming Pro.

‎04-23-2025

*GASP* No way, that can't be!

‎04-22-2025

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.

‎03-08-2023

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 });

‎03-07-2023

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?

‎11-30-2022

Ooh great, I didn't realize that, I'll give it a try... thanks!

‎11-29-2022

Is there an easy way to have the Expand widget show text instead of icons?

‎11-16-2022

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.

‎11-16-2022

//

‎11-16-2022

Is there a better solution than this now? Id' rather not mess with CSS for this. I see Expand has a label property, but I'm not sure what it even does.

‎05-10-2022

We're having an issue with an iPad... we open a route, and then when the user minimizes the app and opens a different app on the iPad and then when they go back to the Navigator app it says "Loading" and then it clears the existing route as if a route was never loaded. I tested this on my iPad and it doesn't do this... it keeps the route loaded even when I go back and forth from apps. Any idea why this other iPad is not doing that and clearing the route?

‎01-06-2022

Talk about unintuitive! Yikes! Who does the UX/UI for this app?

‎11-02-2021

That's the problem though. No one knows and you need to be a super duper extreme power user just to generate a report, which is crazy since it's a survey app -- of course people are going to want to generate reports from the data. Even with the custom templating I don't see how to easily include charts/graphs. Like come on, have some nice looking reports by default. And limiting a report to 1,000 records in this day and age is just ridiculous -- like that's embarrassing. Why make it so you need a PHD and development experience? I thought that's what ESRI was for -- easy solutions for the end user -- but let me tell you, this is NOT easy. We'll just stick with SurveyMonkey or Microsoft products for these needs because, fortunately, they do make it easy.

‎11-02-2021

@RobertScheitlin__GISP thanks, missing the array, also I just realized that I only need to do: view.popup.open({ features: [feature], }); Because the queried feature is getting it's popupTemplate from the sublayer.

My Ideas

Latest Contributions by _____

Re: Why is Pro so terrible after all these years?

Re: Why is Pro so terrible after all these years?

Re: Why is Pro so terrible after all these years?

Why is Pro so terrible after all these years?

Re: Is there a bug with the Search widget for 4.26?

Is there a bug with the Search widget for 4.26?

Re: Expand widget show text instead of icon?

Expand widget show text instead of icon?

Re: Uncaught (in promise) TypeError: Cannot read properties of null (reading 'some')

Uncaught (in promise) TypeError: Cannot read properties of null (reading 'some')

Re: Widen Expand Widget button and display text instead of icon

Clearing route when minimizing app and viewing another app and then going back

Re: How to remove a survey from mobile device?

Re: Report limited to 1000 records?

Re: Opening Popup for feature returned from QueryTask?

Re: Why is Pro so terrible after all these years?

Re: Why is Pro so terrible after all these years?

Why is Pro so terrible after all these years?

Re: Skip to next stop

Re: Is there a bug with the Search widget for 4.26...