Price Property Editor does not work in Block List with inline editing

[arknu]

Which component is this issue related to?

Umbraco Commerce (Core)

Which Umbraco Commerce version are you using? (Please write the exact version, example: 10.1.0)

16.2.2

Bug summary

After upgrading from Umbraco 13, I noticed that the Price property editor no longer works in a Block List editor.

In Umbraco 13 (Umbraco Commerce 13.2.3):

In Umbraco 16 (Umbraco Commerce 16.2.2):

Going to the datatype settings and selecting a fixed store causes the editor to appear. I thus assume that it is somehow not able to locate the current store.
As this worked in version 13, this is a regression.

Specifics

No response

Steps to reproduce

Include a Umbraco Commerce Prise property editor in a block list editor with inline editing enabled.

Expected result / actual result

Actual: The editor is not shown

Expected: The editor should be shown

Dependencies

No response

---

This item has been added to our backlog AB#56191

[mattbrailsford]

I think I know where the problem area might be which will likely be the ability to lookup the parent document from within the block. It's not quite as easy in v16 compared to v13 so we must have missed this use case.

I'll add it to our backlog to take a look at in an upcoming sprint, but it looks like you have workaround for now at least by explicitly setting the store in the property editor settings.

[arknu]

@mattbrailsford Thanks.
Yes, we have a workaround, but it means we now have to specify the store in several places, which is not ideal. So I'm looking forward to a fix :)

[mattbrailsford]

Out of interest, if you change it from being an inline block grid (old nested content style) and be a regular grid with the editor that opens in a modal, does that work without the need of the store being set?

[arknu]

@mattbrailsford Just tested, and yes, that works fine. So it seems only the inline editing mode is broken.

[mattbrailsford]

Excellent. Then my hunch is correct, and you have a better workaround for the time being

[mattbrailsford]

Managed to find and implement a fix, this will be in an upcoming 16.3.0 and 15.3.12 release

[arknu]

Thanks for the quick fix!