You can put whatever property you want in the Properties list of your
SerializableCart. It is just a
object. So no need or way to define custom MetaFields for a
However, when you convert the
SerializableCart to a
PurchaseOrder, the property names and types have to match the known MetaFields on the
PuchaseOrder MetaClass (and related types). So best to use the same property keys as the MetaField names.
If you've already been using non serialzed when converting to serialized everything should work fine as you've obviously already got all the fields set up for non-serialized/purchase orders. It just used JSON serialization, a few points to cadveat to be wary of
I am working on a project that currently uses non-serialized carts, I now need to Enable the serialized carts and make the necessary changes. I am folllowing the below mentioned developer guide article on serialized cart implementation:
The current site (non-serialized) uses a lot of meta fields across a number of classes (ordergroup, orderform, linetitem, shipment, address). I dont think this should be an issue while migrating to seriazlised carts. As I see that that the classes can be extended like the example mentioned in the developer guide arctile below:
So I can use meta fields with serialzed carts right? just that the manner of setting/accessing the metafields is different from the legacy way.