Classification section does not show up on create item screen

[Anders..Boman]

Like the title says, in our tenant we use the classification section to store details about our items. The classification section used to be included on the item creation screen, but it does not show up anymore. See attached screenshots for clarity. Also, the numbering of the sections clearly shows that one is missing.

I have tried to remove the section and re-add it without success. Have anybody experienced this recently, and does anyone know how to fix it?

[tony.mandatori]

This looks like a bug.  There is most likely an error in the developer console (F12 when using Chrome or Firefox).

To resolve this, tech support should be involved. Please open a call.

[giliar.defriesperez]

Hi @Anders..Boman ,

We have a bug being looked at that closely related to this - the section is missing from the Create page. However, the scenario we were able to reproduce involves a class that does not contain any properties (fields), which is not what you have in your screenshot. Can you please file a case for this so we can look at it as a priority? Thanks.

[Anders..Boman]

Hello,

I will open a support ticket. Thank you for your response.

[Anonymous]

It looks like I have the same issue, the Classification Section which is required for our Part Number Generation doesn't show on create Item.

Is this tenant by tenant isolated issue, do I need to follow suit and report a support case?

Bob Donovan

[giliar.defriesperez · Accepted solution]

@Anonymous  @Anders..Boman ,

At around 5PM EDT today (Sept 18th),  we released a fix for the issue that was affecting most customers, and I believe this is the same that you are experiencing based on the posts here. Please re-check the creation of an item in the workspaces affected and let me know if it's fixed for you too - if not, file a support case and send me over private message the case number.

Thanks,

Giliar

[Anders..Boman]

The reply I got for my ticket was that they are already aware of the issue and are working on fixing this bug. I don't think it would hurt if more people report this as that might increase the motivation to fix it.

Edit: I can confirm that my issue is now resolved. It seems to be working as intended now.

BR/ Anders