I am trying to set up our Description Key Sets for Civil 3d. I understand how they work for the most part, but I've reached a snag. Here is my situation:
The trouble I am having pertains the othe "code", I have a description key code set up as "p" for pipe. A raw descritption of "p" alone is recognized, but In my sitiation I have more than one pipe so we used p01, p02, p03 and so forth. When the numbers are added the raw data, the "p" in the description is no longer recognized. Is there any way to get this to work? Should I include a space between the p and the numer? (this would require me going back and changing 500+ raw descriptions manually) Is there something I can add to the description key like p## or p$$ that will recognize the numbers are just for sorting? what is the best way to approach this with minimal work?
Also, side note. I noticed some of the defautl description keys come with a * at the end i.e. GUT*, what does the asteric do? Is it necessary?
Another side note, are the description keys and raw descriptions case sensative? My sureyor was wondering this.
Solved! Go to Solution.
If your pipes always have a number after P, you can use P#, or P##. The * is a wildcard, anything that begins with a P will be matched. Careful not to use ANY other description that begins with a P.
Yes, these are case sensitive.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register