https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/best-practice-for-saving-features-generated-client/m-p/1327194#M82202 <P>I want to improve my code for saving/storing features when they are generated client side, for further clarity, the featurelayer doesn't come from a remote service.</P><P>&nbsp;</P><P>currently I use the&nbsp;<SPAN>applyEdits to listen to changes and then store them as a json string, then act on the string.</SPAN></P><P><SPAN>However this seems, like the unlikely solution considering myriad of gaps associated with applyEdits.</SPAN></P><P>&nbsp;</P><P><SPAN>What is the best practice if user generates a feature layer, and creates new features (using the editor widget in our case), and we want to save the features for future recollection.</SPAN></P><P>&nbsp;</P> Mon, 11 Sep 2023 10:28:16 GMT Aeseir 2023-09-11T10:28:16Z https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/best-practice-for-saving-features-generated-client/m-p/1327194#M82202 <P>I want to improve my code for saving/storing features when they are generated client side, for further clarity, the featurelayer doesn't come from a remote service.</P><P>&nbsp;</P><P>currently I use the&nbsp;<SPAN>applyEdits to listen to changes and then store them as a json string, then act on the string.</SPAN></P><P><SPAN>However this seems, like the unlikely solution considering myriad of gaps associated with applyEdits.</SPAN></P><P>&nbsp;</P><P><SPAN>What is the best practice if user generates a feature layer, and creates new features (using the editor widget in our case), and we want to save the features for future recollection.</SPAN></P><P>&nbsp;</P> Mon, 11 Sep 2023 10:28:16 GMT https://community.esri.com/t5/arcgis-javascript-maps-sdk-questions/best-practice-for-saving-features-generated-client/m-p/1327194#M82202 Aeseir 2023-09-11T10:28:16Z