Schedule: splitting the parameters so that some of them will show up as columns and some as rows.

[danezeq]

i know it unusual but:
i have one family with 220 parameters.

they represent 10 elements (signs plates) which each one of them has 22 "real parameters".
So 10*22 parameters gives 220 parameters.

In schedule each parameter get its own column (220 columns)
while the structure needed is each of the 22 parameters will get its own column while each of the 10 sign plates will show up as a row.

Now, i know the obvious way to do it is that every plate will get it's own family, but then i get another problem which is i cannot include all of the plates in one tag. (https://forums.autodesk.com/t5/revit-architecture-forum/instance-with-incremental-instences-inside/m...)

So, is there an option to split the schedule this way? showing some of the parameters as columns and some as rows?

the structure needed:

Thanks in advance 🙂

[jvpantin2]

Maybe you are tangled with some concepts, as parameters, fields and values. A schedule is created selecting fields from a list of parameters, these fields will be the schedule's columns and they will be ordered from left to right as selected. The rows are created automatically, arranged and sorted (ascending or descending), depending on the fields used. Schedules can also be subdivided by selecting any given field in Sorting/gropung list and hiding it in Formatting tab to remove as column.

So, if I understand you well, there are not 220 parameters but 22 fields, and in this case, the "plates" are all the existing group or instances (values) from a parameter/field (i.g. "family name" or "type name"). Then, the 22 parameters/ fields will be populated in each cell with the values wich belongs to any given "plate", assuming that all instances or group of instances (plate 1, plate 2) share the same value in all fields/column of the schedule. If not, the rows will multiply and you will see the plates repeated at the first column or the text <varies> in cells depending if instances are itemized or not.

Resuming: 1º if a parameter is selected as a field, it will be always a column (unless you use to sort and hide), 2º the rows will be always created upon parameter/field values, in ascending or descending order, 3º the order can be always (and only) controlled using parameters, if there aren't any available others can be created for this purpose. 

[Mike.FORM]

Make all the plate families hosted by your sign family shared. Then they will be loaded directly into the project and you can schedule the plate itself. You should then be able to sort the schedule by using the actual sign type mark.

[danezeq]

you mean familiy inside family? okay! done it! now how can i make the tag to iclude labels for all "front text" parameters from different plates inside?

and one more thing: the family that inclueds the other sub-families (the plates) doesnt report to the schedule each "front text" parameter from every sub-family. i can't see them in the schedule.

[Mike.FORM]

For the scheduling you need to make a shared parameter that you can fill in for the plate families that identifies what sign post it is attached to. Then in your schedule you can sort/group with that parameter and set it as a header.

I don't think there is a way in revit to link the the sign parameter to the plates automatically with shared parameters. You will have to do it manually, or there might be a dynamo script somewhere to do this.

The front text parameter also needs to be a shared parameter if you want it tagable and you will need to tag every plate on the sign post individually by tab selecting them. If you dont need the front text in the tag you could just add them as project parameters instead of shared parameters.

All in all it is possible to do but it is a lot of steps and not as straight forward as you want.

Personally I would only show the info on the plates in the schedule and in plans just tag the sign number.

[Mike.FORM]

Here is what I have done. The first 3 columns are just for organizing the schedule and can all be hidden.

Columns D-G are project instance parameters and can be set to anything you want.

I have attached the sample project (Revit 2022) so you can look at it.

[danezeq]

first of all -Thank you. i'm still not able to understand the structure of it, but i'm trying now.

[jvpantin]

Would you mind to share your family file? So we can have a look and have a closer idea of what are you trying to achieve

[Mike.FORM]

One thing to note is There is a filter in the schedule to not show the family named "Sign" (that is just the post family with the plates). When you are working in your schedule you should remove that filter as there are some parts that need manual input for organizing and it helps to see the Parameters associated to the post family. Also theree is a type for every sign and a corresponding plate type. Without this the organization does not work.

Here is a snip showing the Sign family visible.

[danezeq]

 i see. i'm going to ivestigate it 🙂

[Mike.FORM]

Add then if you add a standard detail elevation showing the plate numbers like this you can indicate in schedule exactly what goes there.