how to project parameters defaulted off

[kgatzke]

I want to add an identity data project parameter to all views so I can track views that need to be cleaned up for a major revision.

I succeeded in creating the parameter only to discover it is defaulted to Yes and checked for inclusion in EVERY view template.  This makes the task of setting the parameter to NO in all the views horrendously complex.  How do I create the parameter so it's defaulted off and not included in view templates?

[barthbradley]

What would make it easier for you, is to just create a schedule a untick all the boxes there. But, as far as for the parameter itself; it's going to be present in every existing and newly created view's properties.  

[ToanDN]

Yes/No parameters are default to neither Yes or No, but Null.  Use "Null" as "Not Yes" or "Not No" toward your favor.

[kgatzke]

@barthbradley the big problem for me is that the parameter has been automatically included (control of has been checked yes) by every view template.  There are over 50 view templates in my current project. The parameters for almost every view were set to Yes, @ToanDN, so the first thing I did was create a schedule to uncheck the views but they're all greyed out by the freakin view template inclusions.  There is a problem with the defaulting.  

[barthbradley]

@kgatzke: They are grayed out because they have no value (Null). They do not have a Yes/No value until you take them out of their grayed out state by  checking/unchecking them.  I know visually they have a checkmark, but if another parameter reads it, the value pulled from it is nothing (not Yes).  

[kgatzke]

I got rid of the parameter because it wasn’t worth the hassle otherwise I’d screenshot you what I’m seeing, which is a grey checkmark I can’t change.  If I select the view the parameter is grey in properties and I still can’t change it because the new parameter is controlled by the view template BY DEFAULT.  That’s the problem.

[barthbradley]

Ha! If at first you don't succeed -- screw it.  

But, seriously, I don't get why it isn't behaving for you. You should be able to add it to a view and control it's value either manually, or automatically by including it in the View Template properties.  

Something is fishy. 

[kgatzke]

So you're saying that normally when you add a project parameter to views the default inclusion for view templates is unchecked?  I get a mix.  Some, I'd say most view templates have it checked, and there are hundreds of affected views.

There was another project parameter already on views that wasn't being used.  It's text but I can filter a schedule for a word like REV.  What's happening is we're on a project that went to bid and the client suddenly decides they need another 20 rooms so it's being issued as a big change order with dozens of revised sheets.  As I and others are working -- moving every type of system family around  -- a lot of elevations, sections and details are being inadvertently modified or entirely destroyed.  I needed a way to tag and schedule views for others to revisit and repair.  When they finish fixing a view they can un-tag its parameter and it disappears from the schedule.  We're done when the schedule is empty.

[barthbradley]

I hope this can help clarify:

View Schedule key:

“ABC”=Yes/No Project Parameter applied to Views

“ABC’s Value”=Calculated Parameter, Text value. Formula= “if(ABC,“Yes”,”No”)

View Templates:

• “ABC Yes”=ABC parameter is Included and is checked
• “ABC No”= ABC parameter is Included and is unchecked
• “ABC Not Included in Template”=ABC parameter is not Include in the template (e.g. it can be check or unchecked in all views assigned this template). Note that this template has been assigned to “Ceiling Plan: Level 1” and the view’s “ABC” parameter has been checked (e.g. null status removed).
• “None” = No View Template assigned. Note that its “ABC” values are grayed out and reporting no value to “ABC’s Value”

[kgatzke]

I'm really sorry but I don't follow your instructions.  I'm having the same problems with your parameters that I had with the ones I created and I think it's because you left out a lot.  Are these parameters shared?  Are they by type or instance?  What type of parameter?  Are the values aligned by group type or instance?  How do I assign the formula to the parameter?  I'm not in a family editor.  

I may be wrong but I think the problem here is I'm creating these parameters in an environment where there are already a lot of views and assigned view templates.  Our BIM guy may have created the parameter I'm using before he created all those view templates because it's not checked in most of them.

[ToanDN]

Forget about that existing parameter.  Create a new Yes/No parameter and assign it to Views category.  It is new so it will not be governed by existing view templates and it is default to Null (grey box).  Use it to tick your views via the project browser or a schedule is up to you.  You can get rid of the existing one.

[Viveka_CD]

Hi @kgatzke

I just wanted to follow up here, any progress on this issue?

Did the recommendations by the experts help?

Please mark any posts that help with "Accept as Solution" and thanks!

[kgatzke]

@ToanDN, you and @barthbradley keep telling me to do the same thing and I keep telling both of you it's not having the results both of you expect.  Any parameter I create is automatically included in existing view template controls.  I don't know why that's the way it is for me and not for the both of you but either there's a setting I don't know about (isn't that my original question?) or you're leaving something out of the instructions.  

[barthbradley]

---

@kgatzke wrote:

@ToanDN, you and @barthbradley keep telling me to do the same thing and I keep telling both of you it's not having the results both of you expect.  Any parameter I create is automatically included in existing view template controls.  I don't know why that's the way it is for me and not for the both of you but either there's a setting I don't know about (isn't that my original question?) or you're leaving something out of the instructions.  

---

 I'm not sure what you mean by: "Any parameter I create is automatically included in existing view template controls." When you create a new Project Parameter, you manually check the Categories to which it applies. In your case, you created a Yes/No Project Parameter and then checked "Views" under "Categories"; isn't this right? If so, that parameter appears in the properties of every existing and newly created View. And, the default setting for that Yes/No parameter checkbox will be null. In other words, the checkbox it will appear as checked and grayed-out initially. This is a null condition; neither Yes or No.  

If you're experiencing something different than what I described above, then perhaps you have another issue going on. Can you share your file? 

[kgatzke]

Yes the parameter is null for all views.

THAT"S NOT THE PROBLEM>

The problem is all the views have templates assigned to them and in almost all of the templates the parameter is included.

If it's included it can't be changed without first UN-INCLUDing it in the template.  There are 72 templates in the project. 

The problem is the automatic inclusion I feel like one of those apes jumping up and down and screaming in 2001 A Space Odyssey trying to explain this to you 🙂

[ToanDN]

I got it.  I think you do need to scroll through the 72 view templates and untick the box for the parameter manually.  It will probably take anywhere from 72 seconds to 720 seconds total.  Unless you want to find a more automated solution from something such as Dynamo, which I am not sure if exists, and I am sure it will take a lot more time than 720 seconds.

[kgatzke]

Sorry for not replying to this sooner, or for approving any post as a solution.  Autodesk did that themselves, otherwise how would they main their reputation as miracle workers without a spotless record for no unsolved problems?  Ticking off those views may not be a problem for anyone who works alone on a hot machine but me, I'm looking at 30-60 second refresh rates on every view change considering our multi-gigabyte file sizes, less than state of the art equipment and aging office network.  That's over half an hour to fix problems like this.  Thank you for the effort, though.

[ToanDN]

You don't need to mark any solutions if you don't see them fit.  Feel free to un-mark.

By the way, to workaround the performance issue, open the file with all workset closed, go to Views > Manage View Templates and make the changes to them.  There will be no refreshing issue since no model elements are loaded.