Latest Contributions by AbiDhakal

@Jianxia - I see Copy & Paste features, Cut, Merge, Reshape. Would you please confirm if the AutoComplete tool is planned to be included as part of the roadmap? This feature is utterly essential for our workflow, and we'd appreciate any updates regarding its availability. Also, we would have to have it for both Creators and Mobile Workers as their fundamental edit widget capability. Thank you very much for all you do. Abi ... View more

@Jianxia -  After such a long wait and so much anticipation, it's incredibly disappointing to see the direction Esri has taken. To promote the new Web Editor application, Esri has chosen to restrict basic editing capabilities that were once available through the Edit widget in Web AppBuilder. This functionality that countless loyal users, including those supporting public-facing applications, have relied on for years. We were doing quite well with what existed. Removing or withholding such a fundamental feature from Experience Builder feels not only unnecessary but like a calculated move to drive users toward a paid solution. This decision comes across as short-sighted, cutthroat, and deeply disheartening. The fact that the original Edit widget still functions in Web AppBuilder, yet remains absent in Experience Builder, only adds to the frustration felt by long-standing users. Worse still, this is happening at the expense of usability and workflow efficiency. GIS professionals and end users once enjoyed a user-friendly, streamlined editing experience in Web AppBuilder. Now, for the sake of licensing, that tool has not only been downgraded in Experience Builder; it has been moved entirely to a separate Web Editor application, further complicating workflows and causing unnecessary disruption. Despite repeated concerns voiced throughout the Esri Community, it seems those voices have not been heard. What was once a core, inclusive capability is now gated behind licensing, effectively betraying the trust of honest, loyal, lifelong users who simply need to perform basic edits in the modern web environment Esri is requiring us to transition into. Esri and its users have long enjoyed a very symbiotic ecosystem, where Esri provides the capabilities, and users contribute honest, thoughtful feedback. In tandem, we have improved and learned from one another. Let us keep it that way and make this a selfless pursuit of capabilities that help the science of geography thrive. Esri is, of course, free to innovate and promote the new Web Editor as a premium offering. But we strongly urge you to also restore the original Edit widget, with its full capabilities, within Experience Builder, and make it available across user types, especially for Creators and Mobile Workers. This is not just a feature request. It is a plea from a dedicated community that has supported Esri for decades and now feels disregarded. Please do the right thing. Restore this essential functionality where it belongs. Thank you, Abi ... View more

After such a long wait and so much anticipation, it's incredibly disappointing to see the direction Esri has taken. To promote the new Web Editor application, Esri has chosen to restrict basic editing capabilities that were once available through the Edit widget in Web AppBuilder. This functionality that countless loyal users, including those supporting public-facing applications, have relied on for years. We were doing quite well with what existed. Removing or withholding such a fundamental feature from Experience Builder feels not only unnecessary but like a calculated move to drive users toward a paid solution. This decision comes across as short-sighted, cutthroat, and deeply disheartening. The fact that the original Edit widget still functions in Web AppBuilder, yet remains absent in Experience Builder, only adds to the frustration felt by long-standing users. Worse still, this is happening at the expense of usability and workflow efficiency. GIS professionals and end users once enjoyed a user-friendly, streamlined editing experience in Web AppBuilder. Now, for the sake of licensing, that tool has not only been downgraded in Experience Builder; it has been moved entirely to a separate Web Editor application, further complicating workflows and causing unnecessary disruption. Despite repeated concerns voiced throughout the Esri Community, it seems those voices have not been heard. What was once a core, inclusive capability is now gated behind licensing, effectively betraying the trust of honest, loyal, lifelong users who simply need to perform basic edits in the modern web environment Esri is requiring us to transition into. Esri and its users have long enjoyed a very symbiotic ecosystem, where Esri provides the capabilities, and users contribute honest, thoughtful feedback. In tandem, we have improved and learned from one another. Let us keep it that way and make this a selfless pursuit of capabilities that help the science of geography thrive. Esri is, of course, free to innovate and promote the new Web Editor as a premium offering. But we strongly urge you to also restore the original Edit widget, with its full capabilities, within Experience Builder, and make it available across user types, especially for Creators and Mobile Workers. This is not just a feature request. It is a plea from a dedicated community that has supported Esri for decades and now feels disregarded. Please do the right thing. Restore this essential functionality where it belongs. Thank you, Abi ... View more

After such a long wait and so much anticipation, it's incredibly disappointing to see the direction Esri has taken. To promote the new Web Editor application, Esri has chosen to restrict basic editing capabilities that were once available through the Edit widget in Web AppBuilder. This functionality that countless loyal users, including those supporting public-facing applications, have relied on for years. We were doing quite well with what existed. Removing or withholding such a fundamental feature from Experience Builder feels not only unnecessary but like a calculated move to drive users toward a paid solution. This decision comes across as short-sighted, cutthroat, and deeply disheartening. The fact that the original Edit widget still functions in Web AppBuilder, yet remains absent in Experience Builder, only adds to the frustration felt by long-standing users. Worse still, this is happening at the expense of usability and workflow efficiency. GIS professionals and end users once enjoyed a user-friendly, streamlined editing experience in Web AppBuilder. Now, for the sake of licensing, that tool has not only been downgraded in Experience Builder; it has been moved entirely to a separate Web Editor application, further complicating workflows and causing unnecessary disruption. Despite repeated concerns voiced throughout the Esri Community, it seems those voices have not been heard. What was once a core, inclusive capability is now gated behind licensing, effectively betraying the trust of honest, loyal, lifelong users who simply need to perform basic edits in the modern web environment Esri is requiring us to transition into. Esri and its users have long enjoyed a very symbiotic ecosystem, where Esri provides the capabilities, and users contribute honest, thoughtful feedback. In tandem, we have improved and learned from one another. Let us keep it that way and make this a selfless pursuit of capabilities that help the science of geography thrive. Esri is, of course, free to innovate and promote the new Web Editor as a premium offering. But we strongly urge you to also restore the original Edit widget, with its full capabilities, within Experience Builder, and make it available across user types, especially for Creators and Mobile Workers. This is not just a feature request. It is a plea from a dedicated community that has supported Esri for decades and now feels disregarded. Please do the right thing. Restore this essential functionality where it belongs. Thank you, Abi ... View more

@LarryYoung - After such a long wait and so much anticipation, it's incredibly disappointing to see the direction Esri has taken. To promote the new Web Editor application, Esri has chosen to restrict basic editing capabilities that were once available through the Edit widget in Web AppBuilder. This functionality that countless loyal users, including those supporting public-facing applications, have relied on for years. We were doing quite well with what existed. Removing or withholding such a fundamental feature from Experience Builder feels not only unnecessary but like a calculated move to drive users toward a paid solution. This decision comes across as short-sighted, cutthroat, and deeply disheartening. The fact that the original Edit widget still functions in Web AppBuilder, yet remains absent in Experience Builder, only adds to the frustration felt by long-standing users. Worse still, this is happening at the expense of usability and workflow efficiency. GIS professionals and end users once enjoyed a user-friendly, streamlined editing experience in Web AppBuilder. Now, for the sake of licensing, that tool has not only been downgraded in Experience Builder; it has been moved entirely to a separate Web Editor application, further complicating workflows and causing unnecessary disruption. Despite repeated concerns voiced throughout the Esri Community, it seems those voices have not been heard. What was once a core, inclusive capability is now gated behind licensing, effectively betraying the trust of honest, loyal, lifelong users who simply need to perform basic edits in the modern web environment Esri is requiring us to transition into. Esri and its users have long enjoyed a very symbiotic ecosystem, where Esri provides the capabilities, and users contribute honest, thoughtful feedback. In tandem, we have improved and learned from one another. Let us keep it that way and make this a selfless pursuit of capabilities that help the science of geography thrive. Esri is, of course, free to innovate and promote the new Web Editor as a premium offering. But we strongly urge you to also restore the original Edit widget, with its full capabilities, within Experience Builder, and make it available across user types, especially for Creators and Mobile Workers. This is not just a feature request. It is a plea from a dedicated community that has supported Esri for decades and now feels disregarded. Please do the right thing. Restore this essential functionality where it belongs. Thank you, Abi ... View more

Thank you for the great work you all do. Please make sure it has add, split, merge, autocomplete. Autocomplete is utterly important. Thank you, Abi ... View more

everything @MichaelTorbett says and autocomplete in the Edit widget is too important. We cannot do anything without the Autocomplete feature. Thank you, Abi ... View more

@Jianxia - Good morning, ma'am! Happy Friday! I have been trying to use a custom geoprocessing tool in Experience Builder to extract data, but I get an error saying  GPSQLExpression Is not supported for now. It would really help the Alabama Forestry Commission if you were able to support GPSQLExpression on the Analysis widget in Experience Builder. Thak you for your consideration. Abi  ... View more

@AzizaParveen1  Hey Praveen, Thank you for your reply. I'm having a bit of a hard time understanding and configuring this widget. In WAB, we used to be able to select the fields we wanted to include in the report for an area of interest, and it would return a list of all the selected field values within that area. Please see the attached screenshots. Select fields for the report: This refers to when the client opens the widget—they are able to choose the fields they want included in the report. In this example, we selected four fields. Output Report: The area where I’ve drawn a red line above the map is a customizable section—we can add custom text there. We can also insert our company logo, but that’s done during the widget configuration stage. More of the Report: In the area marked with the red line, we can include a brief summary. Also, importantly, if you look at the report list below, it displays the values for all the fields and its values selected by the client. If these things are possible is there a way, I can configure it to do that for our users? Thank you, Abi   ... View more

@AzizaParveen1  Hey Praveen, In WAB the Screening widget prints maps and reports without having to publish report templates from custom print widget. All you need is a custom print widget and you are able to print maps and attribute reports. Is that possible in EB or will we have to have a report template published to get any kind of report? Thak you, Abi ... View more

@BrendanBladdickEsri  - I thought I had it resolved. I do not. 1. ArcGIS Online is the host. 2. ArcGIS Enterprise 11.4 3. NAM. We are in Alabama 4. One 5. When I create a new workspace in Online, I do not see that workspace come through in Enterprise. Also, when I leave a workspace from Enterprise and subsequently delete the workspace from ArcGIS Online the workspace from the Enterprise does not get deleted. There is some disconnect. I will appreciate your help in resolving this. Abi ... View more

@BrendanBladdickEsri - I do not see this, Invalid redirect_uri. I would like to solve this with you as well. Please let me know how else I can be of help. Abi ... View more

@BrendanBladdickEsri - I have resolved my issue.  What version of ArcGIS Enterprise do you have? If you upgraded your ArcGIS Enterprise from 11.3 to 11.4, but in your ArcGIS Online under Workspace if you see ArcGIS Enterprise 11.3 then we have similar problems. Please click: Collaboration then Workspace. If you see 11.3 instead of 11.4 then we have similar problems, but if you see 11.4 then we have different issues.  I am interested in seeing what is happing with your situation. If you want to, we can connect on a screen share session. My email is abi.dhakal@forestry.alabama.gov. Please send me an email. Thank you, Abi ... View more