You need to put the shared parameter into your title block as well as your project. Although we just use an instance parameter per sheet as our site information plans show true north straight up and regular plans as project north.

Ps you want to delete your other duplicate posting.

Take a look at utilizing global parameters


Sent from my iPhone using Tapatalk

Thanks for the reply Elton,
Have you tested this approach? I'm pretty sure I've hit that nail on the head and the project information parameters will not drive this angle as desired. I actually just tested this approach with a OTB Revit titleblock and blank template and had the same negative results. Please let me know if I'm missing something here.

Thanks for your reply Mengelmn,
I did look at utilizing global parameters but those will not accomplish the primary task of allowing other disciplines to transfer project standards (project information) into their projects which is why I've proceeded down this path.

Elton's on the money.

I'm more interested in this:
(North) Orientation is handled by the Project Location (set of) properties in a file, you can get the orientation into Project Information (manually, or with data trickery like Dynamo) but once "there" it will be a dumb parameter in Project Information, and (technically) still nothing to do with the "real" orientation of the model file, just an "echo".

If the "only" desire is to have your (in-house?) technicians using an always-aligned titleblock (not the same as ensuring model file locations are aligned by any means); the simplest method would be to distribute a "correct" .rfa amongst all users/teams for use in all their models, reloaded as changes require.

But I do the same as Elton, for the very same reason; the fact that "North" can vary depending on the keyplan in use, and/or the orientation of the plan(s) on sheet - to the point where you may need (many) "norths" per view (rather than per sheet) at which point you're inviting the "need" to have multiple SPs (following your method) for <True North Orientation>, <Project North Orientation>, <Plans turned 90 CW>, <Plans turned 90 CCW>, <Plans turned X>, etc....

Thanks Snowyweston,
I appreciate the response but my question is being (not) answered in a round about way. My question was if project information parameters can drive family geometry (specifically in a titleblock). I realize this may not be your company's workflow but this is a way to streamline ours. We have civil, arch, struct, mech, and elec in house which makes coordinating general information like the "typical" plan north for a project much easier if able to transfer project standards rather than (4) phone calls by the lead technician. In response to dealing with sheets that plans views change orientation from sheet to sheet, this is obviously not desired for multiple reasons but the way we deal with it have a supplementary north arrow which is driven with a type parameter. That north arrow is used supplementary to our sheet arrow. Maybe a more solid approach would be to link up the project north data with a north arrow...is this possible though?
Thanks again for the help!

Pretty sure your answer is no (someone will correct me if I'm wrong) as you can't put project parameters into a titleblock family. We are simply offering alternate solutions to your workflow.

Cant be done, without involving an external app or Dynamo, at which point better just teach them to reload a shared nested family for the N Arrow, and call it a day.

As snowy pointed out, i also wouldn't want to be responsible for a consultant's north arrow.