Latest Contributions by AbiDhakal

@Jianxia  Thank you for the update! The community and I sincerely appreciate you and are grateful for everything you do to make our work easier and more effective. As we look ahead, it remains essential that all core capabilities are fully supported in Experience Builder before Web AppBuilder is phased out in future releases of ArcGIS Enterprise. Keeping Web AppBuilder accessible while Experience Builder continues to mature, particularly during the period where capability alignment is still being reached, will ensure a smooth and low-risk transition. Even after full feature match is achieved, allowing at least an additional year as a buffer would provide organizations like ours the time and confidence needed to migrate our applications without disruption. It simply would not be feasible to retire Web AppBuilder the moment Experience Builder catches up on paper. As we pay close attention to the upcoming release of Advanced Editing widget in Q4 for ArcGIS Online, we hope that it will bring us closer to the editing capabilities we currently rely on in Web AppBuilder. Ensuring that Web AppBuilder apps remain accessible, particularly with the release of ArcGIS Enterprise 12.0 and 12.1, and potentially for some time beyond, is so vital. If Web AppBuilder were to be fully removed with these versions, it would place organizations like ours in a difficult position. We respectfully ask that Esri consider that we may not be able to transition at the same pace. Should that situation arise, we hope Esri will consider providing a patch to backport the Advanced Editing widget to older versions of ArcGIS Enterprise allowing it to be available alongside Web AppBuilder. Without such a transition window, the shift could introduce considerable operational challenges for our teams and for the public users who rely on our applications every day. Respectfully, Abi ... View more

I appreciate your response very much. It is happening during runtime. I tried your suggestion and I still get the same error in runtime. Abi ... View more

I can certainly do that. Please see attached. Thank you very much. ... View more

@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