BOM – Split SIZE column into L, W, H with rounding — how?

What is the repeat region text for the column?  Table > Repeat Region > Switch Syms to show it.

Looks like it is a single parameter being reported.

These need to be separate parameters to compose that parameter or report separately in drawing tables.

dave

You could possibly separate the L W H by scanning the SIZE parameter for the X between the values and create the three parameters you want for your table.

Hi ​@Oguzalp 

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

If so, please mark the appropriate reply as the Accepted Solution or please feel free to detail in a reply what has helped you and mark it as the Accepted Solution. It will help other members who may have the same question.

Please note that industry experts also review the replies and may eventually accept one of them as solution on your behalf.

Of course, if you have more to share on your issue, please pursue the conversation.

Best regards,

Catalina

PTC Community Moderator

You seem to be in a situation where you’re kind of doing things backwards from what would be the simpler process. You’ve got a long string parameter that is probably manually typed in. Now you want to extract the numbers in there to get three values. My preference for this would have been to have three real number parameters that specify the L, W, and H values. I would then use relations to build a string that specifies your SIZE parameter.

To deal with the data format you currently have, a single string, you need to parse that string and pull out the numbers. If you just wanted string parameters for L, W, and H this would be pretty straightforward, using the EXTRACT function. Assuming of course that disciplined entry of the SIZE parameter has been done, and the delimiters are ALWAYS “x”, not any other character, that someone hasn’t made a typo and used “,” instead of “.” for the decimal point, etc. Extra spaces, tabs, or other “white space” can also be problematic.

So, assuming you’re sure the SIZE parameters are all properly formatted, the method I would use to get the L, W, and H values you want:

1. Extract the strings from the SIZE parameter that are textual representations of the dimensions of interest, using three new parameters, maybe txtL, txtW, txtH. I’d use a copy of the SIZE, txtWorking. Find the position of the first “x”, EXTRACT from the beginning of the txtWorking string to the position before the “x” for L, set the txtWorking to the portion of it that follows the “x”, then repeat to extract W, etc.
2. Now you have three text strings that are your W, L, and H so you need to parse them to get the real number values. If there were a STRING to REAL function this would be relatively simple, but there isn’t one.
   Here’s a previous discussion where I had a go at doing this kind of thing.
   https://community.ptc.com/3d-part-assembly-design-327/bom-table-relations-convert-string-to-number-ston-98540
   It’s going to be a lot of repetitive lines of code.
3. You’ll need to process the digits before the decimal point for the integer portion of the numeric value, then do the same for the digits after the decimal for the fractional portion.
4. Once you have a real number for each value, use whatever kind of rounding you wish to get your final integer values for the table.

Regrettably, you are going to have to do this in every model being used in the assembly. You can copy the relations into each model, but still, you are going to have to open each one, etc.

Bear in mind all this is just what I’ve come up with at the moment, you’ll most likely find additional challenges as you attempt to implement things. I’d definitely make myself a test part and try out all the possible data situations you could encounter (what if there’s no decimal point? Is “0.0” handled correctly?)

You’ll probably wish you had originally specified that L, W, and H be input by the part creator, rather than a string.

Good suggestions on the break into separate parameters.

You could use Nitro-BOM to extract the composite parameter to Excel … break it into separate values and have Nitro-BOM create the parameters in each model as an import using the ALL_PARAMS report….  This is trivial… the FREE license can do this.

you can get it here:

https://simplifiedlogic.com/nitro-bom/

Note - this requires JLINK to be installed with Creo Parametric.

Another option would be CREOSON - this would also work just fine… some nice examples of using Claude AI recently highlighted that are pretty slick also.

https://creoson.com/

Hope this helps.

Dave