Forum Discussion
10 Replies
- Yoann_MaingonIdeator Ithat would be the keyed-name In the part itemtype defintion in the properties tab, if you look at the column "keyed name order" you will see that it has a 1 on the line item_number. Just add a 2 in the same column but on the "name" property line. And that will be it.
- Former_MemberIdeator ISuperb, thank you! That does exactly what I hoped. Bob
- jamarIdeator ITo jump on the end of this, is there a way to show this only on the where used, and not everywhere the part number is used?
- RikkyHIdeator I
I would also like a solution to this as this is causing issues around our office.
- AngelaIpIdeator I
It´s not easy to customize the standard Where Used function. But I would recommend you use a TreeGridView as custom WhereUsed option. So you can define very detailed what you want to see in WhereUsed. In addition you avoid that people access ItemTypes they don´t need in daily life or are not allowed to see cause of company restrictions.
- AngelaIpIdeator I
Hi community,
has anyone ever found a way to customize the standard "Where Used" feature? The keyed_name solutions some kind of works, but it still adds Aras ootb revision scheme (which doesn´t fit the revision schema I actually use). And adding the property "name" to the "keyed_name" is also not something to recommend.
I discovered that WhereUsed behavior is mainly influenced by the flimsy "getItemWhereUsed" function which is unfortunately a core feature.
Any ideas?
- FernandoCGIdeator I
Hello, @Angelap, Did you find a way to "customize" the "Where Used"?.
Reading this post, they indicate, I think, how to do it, but I don't see the "keyed name order" column in my Itemtypes. I don't know if my version of ARAS is another or I don't know...
- AngelaIpIdeator I
Hi Meupe,
I think your post were blocked by the spam filter some time ago.
So far I don´t think we can customize the ootb "where used".
Regarding keyed_name and just meant the regular keyed_name properties in the itemtype. But it´s not the best solutions to edit the keyed_names just to get a more detailed WhereUsed view. The keyed_names are used in multiple ways, so it´s not a good solution to add long properties like "name" to them.
One workaround is to use a custom TGV for a WhereUsed view.
Angela