Commerce Datattype Price isn't saving in splitview

[cryothic]

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)

13.1.4 (and still remains after updating to 13.2.1)

Bug summary

It seems the price field isn't saving when you have a page open in split-view.
I have this same issue in Vendr sites too, but I was hoping it was fixed in Commerce.

I have also tried saving field of type Umbraco Commerce: Stock and Umbraco Commerce: Measurements, but they are saved correctly. The only problem I've found so far was with the price field.

Specifics

No response

Steps to reproduce

• Have a site with (at least) 2 languages
• Have a product doctype with a Textstring-field (for verification), and a Umbraco Commerce: Price field.
• Set the textfield to "vary by culture", the price field is NOT "vary by culture".
• Open the product page in the content editor
• Open the second language via split view
• Enter a text in the text field
• Enter a price in the price field
• Click "Save and publish"

Expected result / actual result

I would expect after saving, the new values are in place.

But the price value isn't saved.

If I started with an empty product page, after saving the textfield contains text and the price field is empty.
If I started with an allready filled product page, the textfield gets updated but the price value gets reset to it's previous value.

pricefield_save.mp4

Dependencies

No response

---

This item has been added to our backlog AB#52353

[mattbrailsford]

Can you upgrade to 13.2.1 and see if the issue is still present. Not sure there is anything in the release notes that suggest it would be fixed, but we'd need you to be on the latest v13 anyway before we can look into it.

[cryothic]

@mattbrailsford Hi Matt,
I've updated to Version: 13.2.1.
The problem still exists.

[mattbrailsford]

@cryothic thanks for checking. I'll get this added to our backlog to investigate 👍

[mattbrailsford]

Ok, I've managed to replicate this. Ultimately the Price property waits for a "formSubmitting" event to write it's value back to the model, but it looks like both views trigger that event and so both views cause a save, but the second views wins and so because the value isn't synchronizing, the new value gets overwritten by the old value

[mattbrailsford]

Ok, I've pushed a 13.2.2--preview.2 build to our nightly feed, if you'd like to give that a try I think it should solve your issue.

[cryothic]

Hi @mattbrailsford
I've updated my test-project to the 13.2.2--preview.2 build.

This seems to work. If I now change the price, it get's updated after saving in both views.

I've noticed the field isn't syncing realtime though.
If I change any other field, it instantly updates in both views as if I'm typing in 2 textboxes at the same time.
The price-field isn't doing that.

But the saving self seems to work.

[mattbrailsford]

Ahh, yea, good point.

Just pushed a new 13.2.2--preview.3 build that should take care of that 👍

[cryothic]

That was quick.
Works like a charm now. Thanks.

[mattbrailsford]

Ok great, I'll schedule this for release next week but you are welcome to keep using the nightly in the meantime.

[umbracotrd]

13.2.2 is out now