Culling text in a Schedule Field

[DrakeCanyonArchitecture]

I have a ton of families that have LMBR in the Type Name and would like this to display with just the Lumber Size i.e. "2X4" Rather than "LMBR 2x4". Is it possible to cull "LMBR" out of the result in the schedule rather than renaming all the the Family Types. The other part of this is that I think the LMBR is required for the Add-In that I'm using to work correctly. Alternatively, I figured I could use the another text field such as comments to display the material size, the only thing with that is that if another user adds a material, they won't necessarily know to add the text in the comments field.

[RDAOU · Accepted solution]

@DrakeCanyonArchitecture 

• Leave the type name as is for the add-in (if it is just required for sorting/grouping you can make it hidden as well)
• Add Combined fields in the schedule... and use the parameters for the Base x Height

This way it would populate whenever any new window size is added without the new user doing any extra efforts

[barthbradley]

---

@DrakeCanyonArchitecture wrote:

The other part of this is that I think the LMBR is required for the Add-In that I'm using to work correctly.

---

What's the Add-in?  

[DrakeCanyonArchitecture]

@barthbradley, AGACAD. 

[DrakeCanyonArchitecture]

Thank you @RDAOU. I have to run out right now but will give this a try in a few hours when I come back in.

[DrakeCanyonArchitecture]

@RDAOU, the category that I am using is actually Structural Framing instead of windows. I created a parameter named "Lumber Dimension" and used this formula ---> if(FM d = 0' 5 1/2", "2x6", If (FM d = 0' 3 1/2", "2x4", "2x8"))<---to round the values of FM d to 2x4, 2x6, etc, which worked fine for everything except the header sizes, which can be a variety from dimensional lumber to Glulams. Here is how that looked.

I'm trying to figure out how to use your method with the FM b and FM d fields, which would be similar to Rough Width and Height, except I don't want it to read 0'-3 1/2" x 0'-5 1/2". And even if I get that to read "4x6", When it comes to a Glulam like 5 1/8" x 12", that will present a whole new set of challenges. I'm wondering if creating a field that the user will have to enter the value manually may be the way to go, I really hate to do that though.

[ToanDN · Accepted solution]

1. Edit family
2. Add a number shared parameter (nominal b), use formula = roundup (b/1")
3. Add a number shared parameter (nominal d), use formula = roundup (d/1")
4. Reload family
5. Add combine parameters to schedule: (nominal b) and (nominal d) with an 'x' as the separation

[RDAOU]

@DrakeCanyonArchitecture 

You are currently rounding or standardizing the cross sections using an if statement to 3 specific values...If you want to do that using the combined fields mentioned above, you would either/or:

• create 2x calculated formulas in the schedule to round up the FM b and the FM d parameters then combine (ie: 3 calculated values in the schedule
• integrate those rough/rounded parameters in the family and combine them in the schedule (2 parameters in the family + 1 combined in the schedule) similar to the rough wxh in a door family

The thing is with rounding, one end up with 2 or 3 different cross sections displaying the same rough bxd...for what purpose would this field be used for and wouldn't that be confusing?

And if that is a standard practice why not just use a Type Mark for those types?!

[DrakeCanyonArchitecture]

@RDAOU, agreed with the 3 different values. That worked for every other instance in the wall until I realized that the header changes that whole scenario. And as you and @ToanDN both noted, the shared parameters set to round up and to use them as combined parameters would be the perfect solution, and would even work for dimensional headers. But in the case where the header is a glulam like a 3 1/8"x7 1/2", that would end up reading 4x8. 

Each wall here is an assembly and has a sheet that labels all the parts, cut lengths, lumber sizes (the field that we are discussing), count, etc. I suppose I could exclude the header from the schedule and create a separate header schedule. The thing with the type mark is that even though there can be several types that are the same, the lengths will vary, so the headers are specific to the openings.

As far as all this goes, I suppose the way to go would be to create another column in the schedule with the same combined parameters but don't set them to round up. AGACAD uses something called a sort mark, so the sort mark is specific to the part. I have a meeting with them in about 20 minutes so I will try to bring this up with them.

[ToanDN · Accepted solution]

Here is my 2 cents.

- If you want to keep both lumber and glulam in one schedule then keep their prefix LMBR and GLULAM(?) so the contractor know what is what.

- If you separate them into a lumber schedule and a glulam schedule then use roundup formula to so nominal sizes for lumber  schedule and use true sizes for glulam schedule

[DrakeCanyonArchitecture]

I accepted 3 solutions here mainly because all 3 are viable and work in various circumstances. A combination of the 3 will get the results that I am looking for. As a side note, I did check with AGACAD and there isn't an issue with renaming the Family Types. I thought I had tried that and had issues in the past but they assure me that doesn't cause any problems. Thank you all for your valuable input!