I have the same issue in Commerce 11.8.1. Is anything wrong with the setup Gareth provided?

The worst thing is that there is no documentation how to set up this - no info about CMS nor Commerce:

https://world.episerver.com/Search/?searchQuery=propertylist

This should be the reason it's not working for you

        [BackingType(typeof(PropertyDictionaryMultiple))]

Basically the system does not know how to convert back and forth between your custom type (FaqItem) and DictionaryItem. In this case it's best that you create your own PropertyList type, inherit from PropertyList<T> and handle the serialization/deserialization yourself. 

Good point. I'll see what I can do, 

Thanks, Quan!

In my case, I missed PropertyDefinitionTypePlugIn attribute on my property definition type.

But now I am getting another exception:

EPiServer.Find.Cms.ContentEventIndexer: An exception occurred while indexing (IContent). "[{"filterUrl":"Test","title":"Test","description":"<p>Test</p>"}]" is not a valid value for "Filter header metadata"..
EPiServer.Core.InvalidPropertyValueException: "[{"filterUrl":"Test","title":"Test","description":"<p>Test</p>"}]" is not a valid value for "Filter header metadata". ---> System.ArgumentException: Property value must implement IList<T> or IEnumerable<T>.

My property implements IList, so it looks weird. My property definition looks like this:

[Display(Name = "Filter header metadata", Order = 120)]
[BackingType(typeof(FilterCategoryHeaderPropertyList))]
[EditorDescriptor(EditorDescriptorType = typeof(CollectionEditorDescriptor<FilterCategoryHeader>))]
public virtual IList<FilterCategoryHeader> FilterCategoryHeaderList { get; set; }

The only thing is that this property is on the block and not on the content directly.

What could be wrong with this?

After trying different solutions I tried to add the property list directly to the commerce content and it worked.

So now blocks with such properties are not supported in Commerce.

Yes, you were faster than me. The handling for PropertyList is only for MetaField. Commerce treats blocks as XHTML properties and it does not really look inside of blocks.

Could there be any fix or at least some meaningful exception?

I don't know - there might be some known limitation which I'm unaware of. As always, a seemingly small issue can require a complicated fix - or even a rewrite. I'll file a bug to see if we can do something, but I can't promise anything (just yet) 

Ok. But it should be documented then with a note that property lists cannot be used in a block which is used in a commerce content.

Hi!

Just an update, the bug has been fixed and will be out in next version, probably 12.7.0 (we're preparing for the release 12.6.0 actually).

/B

Hi, Bien!

I am looking at the release info: https://world.episerver.com/documentation/Release-Notes/?versionFilter=12.6.0&packageFilter=EPiServer.Commerce&typeFilter=All

and 12.6.0 does not contain the fix.

Is it released and property lists can be used in the blocks within commerce content now?

It's in Commerce 12.7 which will be published to the feed soon (enough) :) 

It's in Commerce 12.7 which will be published to the feed soon (enough) :) 

Thanks for update Quan!