topic Re: Creo Table -Fixed Index reverting ? in 3D Part & Assembly Design

Creo Table -Fixed Index reverting ?

dweich — Thu, 06 Feb 2025 23:42:10 GMT

In Creo drawings - Tables with “Fixed Index” – these are for BOM’s where if you delete a component, that line in the BOM gets skipped. My company is trying to use this, but it is very quirky. It often reverts back to previous BOM Item numbers. Is there a best practice doc? We’re trying to use Region rather than each Record. I assume someone is using this successfully?

Re: Creo Table -Fixed Index reverting ?

Radovan_DT — Tue, 18 Feb 2025 06:50:24 GMT

Can you please elaborate more. I know that if you delete fixed part from assembly you need to unfix the part which was deleted like this. That way you can "reuse" the table line

Re: Creo Table -Fixed Index reverting ?

anursingh — Tue, 11 Mar 2025 19:39:59 GMT

Hi @dweich,

I wanted to see if you got the help you needed.

If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
Of course, if you have more to share on your issue, please pursue the conversation.

Thanks,
Anurag

Re: Creo Table -Fixed Index reverting ?

dweich — Wed, 19 Mar 2025 22:37:46 GMT

My problem is that my company would like- for example, Item 2- if removed, then 2 will be skipped even if bringing in a new component in the future. I was told this won't happen, unless I manually renumber the table, which I don't want to do. EAC helped me find this - SPR 4428325.

Re: Creo Table -Fixed Index reverting ?

dweich — Wed, 19 Mar 2025 22:38:36 GMT

here is my reply from below - My problem is that my company would like- for example, Item 2- if removed, then 2 will be skipped even if bringing in a new component in the future. I was told this won't happen, unless I manually renumber the table, which I don't want to do. EAC helped me find this - SPR 4428325.

Re: Creo Table -Fixed Index reverting ?

BenLoosli — Thu, 20 Mar 2025 16:44:40 GMT

What I did to preserve the BOM numbering was create a family table of 99 items that have the item set for each one for position 1-99. If you delete item 5, you add to your assembly Deleted Item 5 part, which is an empty part, and then the BOM will show that item as DELETED in the name field and be item 5 in the index. Had to use ITEM 5 instead of just DELETED in the Number field as that would merge the items to a single line.