Darren,
Thank you so much. I and new to GIS and may my question is stupid.
The work flow for my current implementation to create and publish an editable feature service is: Register the table to geodatabase --> Create a Feature layer against the table (MakeFeatureLayer_management) -->add layer to empty map (arcpy.mapping.AddLayer) --> copy map to scratch file --> publish.
My concern is: we need to edit the feature service in other apps by JS rest call, is the copy feature method will syn the data as we expected? if yes, when we set up the env to be hasM disabled, does it overwrite the old data with m values?
The client asked us to keep the old data as it is, and disable the hasM. Not sure if there is a way.......