View Full Version : 2012 room tag displays ? for shared parameter
MikeJarosz
2012-07-02, 09:03 PM
I created two shared parameters and saved them. I then created a custom room tag using the system room parameters and the new shared parameters I created. The shared parameters appeared in the properties window when I selected the room. I was able to enter data there. I created a room schedule and everything displayed correctly including the shared parameters. I then linked the shared parameters to project parameters. The room tag shows blue ? marks when I select the room tags, and blanks when I unselect.
It appears that Revit has the data in the shared parameters, but somehow fails to pass that data to the project parameters to display in the room tag. What am I missing here?
DaveP
2012-07-03, 02:59 PM
Are you SURE that's the right parameter?
I'll sometimes build a schedule with every possible parameter that shows up in the list , just in case.
Also, try changing it from the View - click on that "?" and change it. See if you can figured out what changes in the Properties box.
There is one more possibility - especially with Shared Parameters, it is possible to have two different parameters by the same name. If you Imported the Project parameter from a different Shared Parameter file than the Tag was created from, they might both have the same name, but different GUIDs. That usually happens when the Tag is created at a different time, or if somehow your SP got pointed at a different file.
pfaudler
2012-07-03, 03:08 PM
You cannot simply link shared parameter values to project parameters. You will have to pass on SP values to project parameter or vice versa using API.
Can you please ellaborate bit more with example what you are trying to achieve?
R
DaveP
2012-07-03, 07:17 PM
I I then linked the shared parameters to project parameters.
What do you mean by "Linked"?
Wouldn't you just USE the Shared Parameters?
MikeJarosz
2012-07-03, 07:48 PM
What do you mean by "Linked"?
Wouldn't you just USE the Shared Parameters?
Through "edit label"
86177.
I finally solved it. I should have noted that I started this on the original release of 2012. I then updated to update 2, when all the problems began. My shared parameters originally were "Program Area" and "Program Component". They were the only parameters I had. The parameter text file only had these two parameters. I deleted the parameter text file and recreated it with a variant spelling "Progrm Area" and "Progrm Component". Then "edit label" with the new parameters. (this is what I meant by linked -- it is a link after all). It worked.
Revit never seems to forget a shared parameter once it's been used. After deleting the parameter text file, I thought Revit would lose the previous parameters. So I reused the "correct" spelling and it didn't work. Only after changing to a different spelling did it work.
DaveP
2012-07-03, 08:01 PM
I deleted the parameter text file and recreated it
Yup. That's your problem right there.
I think that if you Remove a Project parameter using the Manage...Project Parameters dialog, it goes away for good, but I'm not 100% positive.
If you do create a new Shared Parameter file, though, you are guaranteed to NOT get the same GUID for ANY parameter you create. That's the "U" part of GUID - Globaly Unique IDentifier
You really want to create one Shared Parameter for the office and have everyone use it. Better yet, have one PERSON use it.
MikeJarosz
2012-07-06, 03:29 PM
You really want to create one Shared Parameter for the office and have everyone use it. Better yet, have one PERSON use it.
I am that one person.
I learned many years ago from James Vandezande to do just that. He kept tight control of the shared parameter file. I am now the BIM manager for a firm with three geographic locations. We are currently setting up Revit server so that we can all work together. Up until now, we have been using FTP to send files to each other and linking them in. Shared parameters under these circumstances are bound to get screwed up. Happily, this situation will soon be over. Until then, I'm going to have a lot of variant spellings.
Powered by vBulletin® Version 4.2.5 Copyright © 2024 vBulletin Solutions Inc. All rights reserved.