It could be related to this fix I put in for handling previously un-documented behaviour in MgFeatureService.UpdateFeatures
http://trac.osgeo.org/mapguide/changeset/6846 But this is just a symptom of a bigger problem. IMO, MgFeatureService.UpdateFeatures is just a poorly designed API that tries to do too many things through a single method. - Jackie -- View this message in context: http://osgeo-org.1560.n6.nabble.com/API-Change-in-MG-2-4-also-Affects-PUT-in-GeoRest-tp4996809p4998464.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
