An asterisk next to a value in a design table seems to indicate that the value is not up-to-date. The asterisk disappears once the associated configuration has been activated but the design table has to be closed and reopened for that to happen. The question is, is there a way to accomplish this without cycling through all configurations before opening the design table?
*Bump*
I'm not getting it either. I'm in SW2010 with the same problem. Hopefully, I can add clarity to this and not hijack/derail Mike's issue. As I tried writing this out I am now thinking that I may have partially answered why the asterisks are used (see below), but I’m pretty much at the limit of my comprehension on this topic… good look making sense of my nonsensical digression:
I took over a part file with configurations built by a Design Table from another engineer and I get asterisks in some of the fields for each of the non-activated configurations. I can temporarily force values to write into excel by manually rebuilding each one of the configurations before loading the DT (as Mike stated). I did this thinking the newly pushed values in the table would remain static until next time the model updated and pushed new values to the table; it does not. After closing the part file and then moving on to its where-used assembly and BOM table the values drop out once again. I guess the table and dependent formulas within it would be unable to obtain the new SW information until the DT is once again reopened and maybe this is why the DT adds the asterisks to protect against this (since opening the DT pulls information from the part file and then closing the table pushes the custom props to update)? In other words, I’m proposing the configuration specific Custom Properties would otherwise never update until individually activated.
I tried to create a part and assembly example for this post and cannot seem to recreate a situation that would show the asterisks. Instead, my new example (“BOM Assembly.sldasm” & “Tube Configs.sldprt”) only shows the original formula I used to drive the custom properties and never change to the evaluated values from the model. Maybe the original part “beam22.sldprt” used a different formula in the DT to pull “SW-Weight”? Looking in the file properties, it appears the expression to evaluate are one-in-the-same, "SW-Mass@@exterior, long, 22"@beam22.SLDPRT".
Issues I’ve found:
p.s. how do I attach file to this bad boy? Here is a link: https://dl.dropboxusercontent.com/u/58915303/SW%20DT%20config%20files.zip
n/m I now see the attach file option after editing. I'm leaving the link too if that is somehow useful.
Message was edited by: James Luntz