Label matching project information

[GoldenGateNetwork]

Good afternoon dear Mentors. 

I created a single file where I can manage 7 projects at the same time. When you open my title block family looks like this:

As you can see there is a lot of overlapping texts, lines, labels and annotation images controlled by visibility in order to obtain different title blocks for cover sheets, floor plans, electric, plumbing, etc.

I had to create 7 groups of shared parameters gathered in the project information looking like this:

For the other hand, I created an annotation family to be placed in my site plans, this annotation have 7 overlapping labels (controlled by visibility yes/no) with the shared parameters "project 1 start date", "project 2 start date"... up to 7, this annotation family is a different file from my title block.

I want please to know what is the formula that I have to apply in order to get the same from project information like this:

any suggestions please?

Thank you very much

[barthbradley]

---

@GoldenGateNetwork wrote:

I created a single file where I can manage 7 projects at the same time.

---

What do you mean by manage 7 projects in a single file? 

[ToanDN]

So you just need to swap 7 project information within one model? If so there is a much simpler way than the way you are doing it.

[GoldenGateNetwork]

@ToanDN , thank you for your information but I do not know a simpler way to do it.

[GoldenGateNetwork]

@barthbradley , yes, 7 projects in a model file.

[RobDraw]

---

@GoldenGateNetwork wrote:

@ToanDN , thank you for your information but I do not know a simpler way to do it.

---

Why don't you ask him?

[ToanDN]

Create 7 blank projects with different project information. When you need to swap information, simply transfer project standards and choose only Project Information category.

[barthbradley]

---

@GoldenGateNetwork wrote:

@barthbradley , yes, 7 projects in a model file.

---

Yah, I heard you the first time.  My question was: "What do you mean by manage 7 projects in a single file?"  

[GoldenGateNetwork]

@barthbradley @ToanDN @RobDraw I am attaching my File where I manage 7 projects. I do not really understand your questions, back and forth, I just need please my question to be solved.

https://www.dropbox.com/s/q56rt1uappmt8cl/Golden%20Gate%20Disegno%20Central%20-%20Copy.rar?dl=0

thanks 

[GoldenGateNetwork]

@ToanDN, @barthbradley, @RobDraw  thank you for the information, but creating 7 blank projects is what I want to avoid, that's why I created just ONE where I can gather 7 projects information and name sheets accordingly.

Please find attached my shared parameter file containing 7 groups of parameters.

This is my project, containing my parametric title block, it's my gift to you helping to solve my doubts and teaching me.

https://www.dropbox.com/s/q56rt1uappmt8cl/Golden%20Gate%20Disegno%20Central%20-%20Copy.rar?dl=0

When I used to have several files/models and I needed to update my parametric Title block I had to open 4 or 5 files/models containing my parametric title block and I had to wait forever 4-5 times for the parametric title block to "Overwrite the existing version" Now, I only have to wait forever once. {this will hopefully change as soon as I upgrade my computer 😉 }

[ToanDN]

Why would you want to avoid an easier way to accomplish the same thing?

[yes_and_no]

This reminded me of myself 30 yrs ago telling my boss, "my AOL Id is UR2Q4M". My boss said, "what wrong with your name ?".

- what s wrong with doing 7 separate project files ? I would ask myself if I were you.

[GoldenGateNetwork]

I am impressed. wow

[GoldenGateNetwork]

@yes_and_no I have already explained several times. your IQ is highest than mine, so I have to go for the most complicated way to do my work and one of them is having O N E file instead of 7.

[ToanDN]

Your model for all 7 projects in ONE file. The 7 blank files are to hold the project info in order to swap them using transfer project standards. It a couple of mouse clicks to get the job done without having to manage 7 sets of shared parameters and their visibility boxes, and no time lag like you described using your method.

[RobDraw]

---

@GoldenGateNetwork wrote:

creating 7 blank projects is what I want to avoid, that's why I created just ONE where I can gather 7 projects information and name sheets accordingly.

---

Why would you want to avoid the easiest and fastest solution?

[mhiserZFHXS]

The reason you're getting so many questions is because what you're doing doesn't make sense. Having 7 projects in one model is NOT a normal workflow.

The reason your title block takes so long to update is probably because of all of the (pardon my language) crap you have on there. It looks like you have included a bunch of information in the family that would only be included on a few sheets, or maybe even just one, in each project. The better workflow would be to remove all of that stuff that wouldn't be on at least a majority of sheets, and then create a template project that has all of that information placed on the appropriate sheets IN PROJECT rather than in the family.

This seems like a classic case of over-engineering families unnecessarily. And now you're trying to over-engineer even more to fix your over-engineering caused problem. Sure, congrats on figuring it out, but you're seeing why this is a problem.

[ToanDN]

---

@mhiserZFHXS wrote:

The reason you're getting so many questions is because what you're doing doesn't make sense. Having 7 projects in one model is NOT a normal workflow.

---

We actually are working on a model that needs 4 different sets of project information due to the entitlement and legality requirements.  Using the transfer project standards method is pretty much painless without even touching the tileblock family.  I can't imagine managing 3 more sets of shared project info parameters and their visibility, let alone 6.

[mhiserZFHXS]

---

@ToanDN wrote:

---

@mhiserZFHXS wrote:

The reason you're getting so many questions is because what you're doing doesn't make sense. Having 7 projects in one model is NOT a normal workflow.

---

We actually are working on a model that needs 4 different sets of project information due to the entitlement and legality requirements.  Using the transfer project standards method is pretty much painless without even touching the tileblock family.  I can't imagine managing 3 more sets of shared project info parameters and their visibility, let alone 6.

---

I may be wrong, but this doesn't seem like the reason OP is doing this. Based off of the little info they've provided, it seems like they have 7 unrelated, or at least different, projects in one model, and the issue they're trying to solve is just that they've over-engineered their title block. Good to know this is a way to handle changing project info for a single project.

[yes_and_no]

To be fair, I had worked on 4 small  models in one project file, but that was only for starting, to save time importing repeated families...But after that initial build-ups, we still need to split up the projects right before setting up the sheet step.

Pls forgive me if the OP mistakenly called me as "highest IQ"...(Intelligence has limitations, but stupidity has not, Albert Einstein).