Issue with M-Values Resetting When Using the Edit Tool in VertiGIS Studio Web

Greetings,
We are experiencing an issue with m-values when using the Edit Tool in VertiGIS Studio Web. Specifically, when a user performs an Edit Feature or Edit Result, it appears that the m-values are being reset to zero if they are enabled.

Details:
I believe this problem is related to how VertiGIS edits a feature. It passes a “adds, updates, geometry, deletes, and attachments.”

The VertiGIS Web payload sent during the edit operation looks like the following:
[  {    "id": 3,    "adds": [],    "updates": [      {        "geometry": {          "hasZ": true,          "spatialReference": {            "latestWkid": 3857,            "wkid": 102100          },          "paths": [            [              [-XXXX, XXXXX],              [-XXXX, XXXX]            ]          ]        },        "attributes": {          "OBJECTID": 287542,          "Something": "XXXXXX",          "Shape__Length": 671.805615666761        }      }    ],    "deletes": [],    "attachments": null  }]

In contrast, the ESRI payload using the Portal Viewer is different is just pass the attributes only:
[  {    "attributes": "ADD something: XXXX",    "Shape__Length": 17261.268679897003  }]

Question:
Is there a way, perhaps through a custom command, to prevent the geometry from being updated in a way that strips out the m-values? It seems that this geometry update is causing the m-values to drop (IMO) , whereas the edit tool in Portal does not have this issue.

Additional Information:
VertiGIS Studio Web is resetting m-values to zero when editing features.
The issue does not occur when using the edit tool in ESRI Portal Viewer.
The difference in payload structure might be contributing to the problem.

Any assistance or guidance on how to retain m-values during the edit process in VertiGIS Studio Web would be greatly appreciated.

Thank you!