This is the part number in my part's properties: M25988/1-044
It displays in the bom, however, as: 1021417"
Mike, it would be hard to guess without looking at the files but check the configuration properties for that part at both places (pics below) and make sure it is not set to different value or have a duplicate value in Configuration properties (under file > properties)
Most probably there is duplicate properties by name "PIN' and "DashNo" in configuration specific properties.
No, it's nothing like that. If I change the value of PIN slightly (add a space somewhere or an extra number) I'll get a completely different crazy number in the BOM. No duplicates in properties. I think it's a bug, but would be nice if someone could duplicate it. I'm using SW 2014. There's something about the backslash and dash that SW goes whacko about. I was just wondering if I had stumbled on some formatting tricks that I just didn't understand. I gave the formula of what I'm doing above. Would be nice if someone could try concantenating two variables like I did, and put in the same value and see if it does it for them. This is not just limited to one file. Any bom that has that milspec number (or one like it) confuses SW for some reason.
By playing around with different combinations, I found one that displays correctly, but still doesn't make any sense to me. Just thought it was some undocumented formatting trick or something, that made SW think it was a date, or equation or something I didn't understand.
I can replicate it in SW2014 and it seems to be a bug or some formatting thing. Please report to your VAR.
So I would suggest to concatenate the properties in the model itself rather than in drawing using equations
Thanks. At least I know I'm not going crazy. Can I combine the variables in the property tab builder?
Yup, BOM table goes bonkers when it sees "/[number]" in PIN properties. Tested in SW2015.
OK, Thanks. I added the variable in the tab builder so the custom property will be created automatically, and will change my bom to call out that property instead of equation. Crazy that I have to do that. Sad to hear that's not fixed in 2015. We'll be updating to 2016 later this year. Can anyone confirm this bug has been fixed in 2016 or not?
Same behavior in 2016. Please report to your VAR so that they can investigate the issue.
Check your Component Property Dialog Box -
Check the Custom Tab and the Configurations Specific Tab, there could be a chance that there the same Custom Property has different values, and check the Drawing Custom Property Tab as well..
Retrieving data ...