Announcement

Collapse
No announcement yet.

Central Model Path in Titleblock

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Central Model Path in Titleblock

    Does anyone know a trick to utilize Global Parameters (or anything else really) that will map the Central Model Path to the titleblock?

    The Default 'File Path' parameter gives you the local file path... not so helpful. I currently have a Shared Parameter (G_CentralModelPath) that is mapped to a label in the Titleblock. When you bring the Shared Parameter into the project, the only way to pick the 'Sheets' Category is if it is an instance parameter. This means you need to edit the Instance Parameter on every sheet. I was hoping to somehow tie a matching Global Parameter to the Sheet Instance parameter so you input the value once and all sheets get the value. However it seems that linking that Instance Parameter to a Global Parameter is also Instance based.

    Thoughts?

    #2
    Select titleblock > select all instances in entire project > update parameter.

    You could get Dynamo to do it for you...

    https://forum.dynamobim.com/t/file-p...tral-file/5123
    There are no stupid questions, only stupid people

    Comment


      #3
      I've often wondered who is meant to benefit from putting the file path on a printed sheet. The only people who can actually use the information are probably already working on the project and in the office that is working on it; and likely to be familiar with project file/folder protocol. A contractor can't access the file with path information, nor anyone else outside the office. The file name could be useful if someone has a copy of the file(s). The path just seems like a useless trivia to me.

      Comment


        #4
        Originally posted by elton williams View Post
        Select titleblock > select all instances in entire project > update parameter.

        You could get Dynamo to do it for you...

        https://forum.dynamobim.com/t/file-p...tral-file/5123
        Yes I agree that a single transfer of data at some milestone would work, utilizing Dynamo or some other means, would work... but I am looking for a solution that allows us to set the value a single time and be connected to the sheets without any copy / paste efforts needed, by human or computer. Any sheets created after the 'transfer' would result in a blank field and the process would need to be repeated.

        Originally posted by Steve_Stafford View Post
        I've often wondered who is meant to benefit from putting the file path on a printed sheet. The only people who can actually use the information are probably already working on the project and in the office that is working on it; and likely to be familiar with project file/folder protocol. A contractor can't access the file with path information, nor anyone else outside the office. The file name could be useful if someone has a copy of the file(s). The path just seems like a useless trivia to me.
        I am looking to use this in (2) different locations. The first is the Starting View that utilizes a sheet. It displays the central model path along with a bunch of other basic project information. This would be primarily useful for project files that have been transmitted or the file reused to point back to the original path. The second would be the at the binding edge of the printed sheet. While I do not disagree that these bits of data seem superfluous it is something that is being asked for due to 'legacy'...

        Comment


          #5
          Originally posted by Steve_Stafford View Post
          I've often wondered who is meant to benefit from putting the file path on a printed sheet. The only people who can actually use the information are probably already working on the project and in the office that is working on it; and likely to be familiar with project file/folder protocol.
          I view it as a type of process check, like the registration marks on a print job. Assuming things are OK, you won't see anything exciting here.

          However, it also benefits those that own the information, but did not necessarily create it. Especially if those that created it are no longer available.
          Chris Ellersick

          Comment


            #6
            The only thing I consider practical or useful about seeing a file's path on a printed page or PDF, when it (the source file) belongs to someone else (the path, network) is to help define how the related files are stored relative to each other. Such as, each trade is in its own trade folder or all together in the same folder. That makes it a little easier to fix the path of files that are not found, for example, assuming they've been sent to me so I can do things with them.

            If I see the file path listed on a Starting View that would help me know where it is supposed to be located if it is not found. As I wrote earlier, the only people who are in a position to benefit from this file/folder information are those who work on that network with the original files. In that instance it is of no help if it is on the printed page that others outside of our firm see.

            ... Legacy...so many things because legacy... yeah I know, picking your battles.

            Comment


              #7
              Yes... this is very much a 'picking my battles' conversation. I'm trying to compromise with them as painlessly as possible. Its unfortunate that Revit doesn't want to play nice without some sort of 'extra' solution (API or Dynamo based)

              Comment


                #8
                It plays nice in what it was designed to accomplish. When we push outside of that box we should expect some extra work.

                I know everyone wants to compromise away from a pure Revit workflow, whatever that means to people, but when you do all you're doing is telling people it's okay to not use Revit as well as it can be used. People need to let this sh*t go and get on with designing amazing buildings and wowing their clients.

                You adapt to the tool as much or more than the tool adapts to you.
                Greg McDowell Jr
                about.me/GMcDowellJr

                Comment


                  #9
                  Since it is fixed information most of the time. The starting view could just use Text, and the title block family could also use text, to show the path. Define it...forget it until the EyeTee department rolls out the brand new cool beans server and everything changes.

                  Did you try using a Shared Parameter assigned to Project Information? That can be used to store this path, making it easier to update everywhere...because that is regarded as Type information when used on a sheet, in contrast with a parameter assigned to Sheets (instance).

                  Comment


                    #10
                    The old school concept of "putting the file path on the binding edge of the printed sheet" was always hilarious to me, but even moreso in Revit. Especially since firms all have different printing and plotting standards. For instance, when its an official issue of documents, i tell project teams they MUST have an archive of the model at that point in time, in case we ever need to reproduce those documents. One of the ways i try to "make sure" they do that, is to have them archive the model BEFORE they plot, and plot from the archived model.

                    At which point the path changes at every sheet issuance. I wonder if we would need to cloud it too? LOL
                    Aaron "selfish AND petulant" Maller |P A R A L L A X T E A M | Practice Technology Implementation
                    @Web | @Twitter | @LinkedIn | @Email

                    Comment

                    Related Topics

                    Collapse

                    Working...
                    X