Hide SKU field if it's being dynamically generated

[andris-sevcenko]

Created by: Lindsey DiLoreto (lindsey@doublesecretagency.com) on 2016/04/27 00:03:34 +0000
Votes at time of UserVoice import: 8

---

It's awesome that we can dynamically generate an SKU! This is (obviously) reminiscent of dynamically generated titles on Entries.

However, the SKU field still appears, with a red asterisk denoting it as "required". It would be great if it followed the pattern of Entry titles, and the field were simply hidden if it's going to be dynamically generated.

Thanks! :)

[andris-sevcenko]

Created by: Anonymous (shawna@imarc.com) on 2017/04/17 18:30:59 +0000

---

Alternatively, I'd also support making the SKU field non-required when generated values are available so that it can be overwritten for whatever reason, with helper text explaining that entering a value will overwrite the generated SKU value

[andris-sevcenko]

Created by: outline4 (s.a@outline4.ch) on 2017/06/21 20:18:37 +0000

---

• 100

[andris-sevcenko]

Created by: Stephen McIver (spm999@gmail.com) on 2017/12/01 17:36:17 +0000

---

I thought it was a bug that the SKU field still appears as required when it's supposed to be dynamically generated! Please fix this bug/add this feature (delete as appropriate). (-:

[nfourtythree]

SKU fields now no longer show for new products or variants if the SKU will be automatically generated.

This code has been pushed and should be included in the 2.2 release.

[spacemanup]

Thanks a lot. But now my workaround doesn't work anymore. My SKU consists of the product ID and the variant ID. So far I had assigned a temporary SKU first, deleted it in a second step and saved the product again. However, this is no longer possible and I can't create new products anymore.

[nfourtythree]

Hi @spacemanup

In theory, this kind of process will still be possible.

How were you assigning your temporary SKU?

[spacemanup]

Hi @nfourtythree, I just type random numbers into the input field :) I guess the hook for the sku fires before the id for the variant is created. Is this correct? I've a plugin that extends commerce, so if you could point me to the right direction, I could probably add a new function to get the sku set correctly.

[nfourtythree]

You could definitely get this working.

If you use the Elements::EVENT_BEFORE_SAVE_ELEMENT event to check to see if the element is a variant, isNew is true and that the SKU is blank. If these conditions pass you could set the SKU to a random string prefixed with TEMPORARY- for example.

Also listening on that same event you could check if the element is a variant, isNew is false and the SKU starts with TEMPORARY- if it does you could blank the SKU field and then let the auto SKU format do the rest of the work.

Hope that makes sense

[spacemanup]

That definitively makes sense! Thank you so much for this fast and very helpful answer!