it's simply not a supported FDO data type, you could try creating a view which returns the XML as a string?
even if it was supported, you would still need to do some custom coding for it to be handled in the properties pane On Tue, Sep 18, 2012 at 11:33 AM, Jamo <[email protected]> wrote: > I've just managed to get an xmlfragment property type populated in my sql > database but sadly it would seem it isn't supported by default in the fdo? > can anyone confirm or deny this is true and any ideas on how to get it > implemented on the mapguide side of things? > > So I now have the ability to store a xmlfragement and idealy anchor off this > in the properties pane rather than my current way of having two comma > seperated attributes (this becomes unstuck as the data get further > populated). > > > > > -- > View this message in context: > http://osgeo-org.1560.n6.nabble.com/quick-one-regarding-mssql-tp5002497.html > Sent from the MapGuide Users mailing list archive at Nabble.com. > _______________________________________________ > mapguide-users mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/mapguide-users -- Zac Spitzer Solution Architect / Director Ennoble Consultancy Australia +61 405 847 168 _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
