Sort fields in Classification Manager for desired order in Item Details

[Anonymous]

Hey Fusion Lifecycle Team,

It would be really helpful to be able to sort the fields created in the classification manager in a right logical order AND display them in exactly this order in the Item Details tab of the record where you refer the classification manager fields.

It seems to be an easy fix, I am sure the entire community would benefit and appreciate if you guys can make this happen.

Let me know of you have further questions regarding this request

Best Regards,

Tim

[fred_smith]

What would be the "right logical order" for you? If ordered alphabetically by field name, I can imagine scenarios where more important/common attributes are mixed randomly among less important/common ones, making data entry, and even use, less efficient. And, what order should attributes be in if the labels are localized to a different language? 'Seems we may need the object designer to provide a priority order on each attribute (a less easy fix?). Thoughts?

[Anonymous]

It would be great if the Admins can design / customize their own field structure order, in the same way as they are able to do in the Workspace Manager for the item details.

A further question I came across is:

I would like to understand how these fields are ordered right now? What determines the order, is it the date / time these field got initially created in the system or is it just a random allocation?

Thanks

[Anonymous]

"Drag to order" (identical to the Workspace Manager's Item Details functionality) would be fantastic.

Right now the field order in classification manager is alphabetical, but on the UI side fields show up in the order they're created, last created going to the bottom of the list. I think I've also observed editing a field puts it at the bottom of the list. The order of fields is important to most companies, trying to adjust the order involves archiving and re-adding fields. It is quite cumbersome.

[Anonymous]

Thank you for this explanation . Wow that is really cumbersome indeed, but if that is the way to achieve this then I need to go that way for now.

Are the software engineers working on solving this odd behavior and missed functionality?

[Anonymous]

FYI: I tried to edit the classification manager fields to change the order they are presented in item details UI, actually the edit does not change the order. I suspect they just stay in the order based on their create date/time. That is a pity.

[giliar.defriesperez]

Hi all,

Yeah, this is something we want to improve on - I understand that the current limitations are not exactly ideal. Just to elaborate a bit further, it's not as simple as it seems: since properties can be inherited by other classes (either sibling or children), re-ordering them could (or not) affect the "original" instance. Also, when determining the order of new properties, we would have to account for shifting the order of the others as well (which can lead to unwarranted changes, making it more confusing for users).

I don't want to get too much into the weeds, but the way I see is having some sort of "Classification fields manager", where you could re-order all the properties in your tenant, and have that order persisted across classes. It's something we are looking into, and I'll make sure to ask for some feedback down the road.

Thanks,

Giliar de Fries Perez

Product Owner - FLC 360

[benderk]

Thank you for submitting your idea. Have you tried the Modern Interface lately? We request that you review your idea in the context of the Modern interface. If your idea is not addressed, we invite you to create a new Idea in the context of Modern so that it can be addressed accordingly. Sincerely, Keri Bender | Global GTM Business Strategy Manager, Product Lifecycle Management

[marco.mirandola]

this topic is quite relevant for all our customers. The ability to set the order to the classification properties is important for 3 reasons:

1. relevance: as mentioned in other posts here, relevant properties should be on top

2. consistency: if the property "material" is the second in one class, it should be also the second in an adjacent class, as the user gets used to having a certain property at a certain place, and inputs the data "blindly"

3. we usually build the description out of the classification properties, so the order matters

we are getting more and more customers in manufacturing, who love the classification capabilities but are stuck by the limitation from a UI and search point of view. How can we get more attention to this topic?

thanks

[timo_ratti]

Described issue becoming a real challenge to end users, since the updating of  class relevance is practically impossible.  Any possibilities to study this case more by the developers?

[Aron_Thorfinnsson]

I get demotivated to see it is more than 8 years since this topic was raised initially.