Automatically generate SKU (OCC-431)

[infofromca]

Is your feature request related to a problem? Please describe

Automatically generate SKU, so the site do not bother the admin to add it which will make mistake and time consuming.

Describe the solution you'd like

use "sku_"+GUID

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

Jira issue

[hishamco]

I already created the AutoIncrement part a long time ago. If there's no problem with having a dependency on an external library, I will make it open to Orchard Core Contrib (OCC)

[sarahelsaig]

This is only applicable if the SKU doesn't matter (i.e. not coming from an outside system and doesn't need to be displayed on the invoice), otherwise it's better to keep the field as manual fill required.

So I suggest a site setting switch to enable, and then a simple content handler to assign ContentItemId to the Sku if it's empty or whitespace after publish.

[Skrypt]

I'm using TENANTNAME_UID because I will eventually need a global shopping cart for all tenants. Also, I don't want to let anyone change this logic because else it would break the product discoverability. I think what you want is a generated SKU for the system. And a free form SKU for the user to match it against his own inventory SKU.

[sarahelsaig]

I don't want to let anyone change this logic because else it would break the product discoverability

Interesting consideration. In this case instead of a site setting, maybe we should add some kind of ISkuProvider. Then you can create this logic in your custom implementation and force enable the associated OC feature, so it's applicable in all tenants.

I think what you want is a generated SKU for the system. And a free form SKU for the user to match it against his own inventory SKU.

Not really, that would be a huge breaking change. Also this doesn't really make sense to me, because content item ID already exists/

[Skrypt]

I know, that's why I did a frontend React app that generates the SKU for inventory management. But the ContentItemId doesn't tell which tenant the product comes from either. That's a struggle.

[canadacubachina]

This is only applicable if the SKU doesn't matter (i.e. not coming from an outside system and doesn't need to be displayed on the invoice), otherwise it's better to keep the field as manual fill required.

manual means easy mistake.
For invoice , it is ok to show the system generated unique code ( or just string processed)