I am trying to find out if there is a character limit on the design table header for example "$configurations@xxxxxxxxxxxxxxxxxxxx<1>" .
I had some trouble with a few files today and once I reduced my file name characters, the error popping up saying the value was invalid went away
Hey Ruben,
Can you try a long name to see if you have this on your side?
$configurations@000-000-000-000-000-000-000-000-000-000-000-000-000-111^part-000-000-000-000-000-000<1>
I will show you one DT of I make...it isn't too long as yours. Please attach your file, maybe I will fix it for you
Thanks Ruben,
But I just was trying to find out about the header name length. I think I will just shorten the names and keep moving forward.
It will add some time, but I will manage.
Yes, I’ve seen DT issues that I thought are related to Configuration@xxx... character limits but can’t be sure and have never been able to verify exactly what is going on. The issue I see is that the configurations do not always update correctly per the other values in the design table. It’s as if at some point SW stops reading DT values, like it does when it finds a cell syntax error, but doesn’t tell you that there are any errors. I shortened and removed all spaces and non-alphanumeric characters from configuration names. Now, all of my configuration names are strictly alphanumeric only with 15 or fewer characters. This seemed to help at first but the issue remains (sometimes).
I hope others can join this discussion because unreliable design tables are a big deal for our models.
I have seen that too, This weekend I made a bunch of changes to my models to prevent any errors.
I have a assembly that is driven by a SSP part, that part has a design table that is driving my global variables.
My assembly just selects the configurations I made in the SSP design table. That is the simplest form I could make.
My part numbering issue is due to my company not having a database so it causes longer part names. But I can work around that too.
So I can shorten the name if I have to, just trying to avoid it if possible.
rename the length of the file, give a name as 000-000-000 or something numerical or alphanumerical code, it will be helpfull to your problem I think