Announcement

Collapse
No announcement yet.

Shared Parameter Conflict

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

    Shared Parameter Conflict

    I am looking for resolution to an issue i'm having. I have tried to bring a family in from manufacturer website and i am getting the following error when trying to load. "The shared parameter "eb8052e8-d47c-4de2-992a-5b7f89756df4" cannot be added with name "Product Page URL" and type "Text" because it conflicts with the existing name "Product Page URL" and type "URL"." Can any one help out with this issue. I am using Revit 2018

    #2
    If you can open the family by itself in Revit, do so, and delete the offending parameter. Then load it into your project.

    Your project has a shared parameter "Product Page URL" that has a URL type, and your family has a shared parameter of the same name, but different type.

    Comment


      #3
      Ok, I understand that much but im not finding where to find it in my project and also how to correct the problem so that i can load the family and use it.

      Comment


        #4
        Shared parameters are on the Manage tab. Product Page URL is under the "Identity Data" group.
        But I would not delete the parameter there.
        I would delete it in the family. (If you want, you can add it back to the family with a "URL" type.)

        Comment


          #5
          I have done that and also when looking at it it says it is a URL type.

          Comment


            #6
            Okay, I'm stumped.

            Comment


              #7
              I'm pretty sure URL is a built-in parameter that can't be deleted or changed.
              Revit for newbies - A starting point for RFO


              chad
              BEER: Better, Efficient, Elegant, Repeatable.

              Comment


                #8
                You can make URL shared parameters too. I think in this case its just very unlucky that there is already a parameter with the same GUID. Or both parameters come from the same manufacturers families and they changed the shared parameter type from Text to URL at some point.. (They would have had to edit this in their shared parameter file).

                The solution is; Dont load crap families that you find on the internet....
                "One must imagine Sisyphus happy." Albert Camus - "The innovator has for enemies all those who have done well under the old conditions, and lukewarm defenders in those who may ​do well under the new." Nicolo Machiavelli -"Things that are too complex are not useful, Things that are useful are simple." Mikhail Kalashnikov

                Comment


                  #9
                  Conflicting shared parameters

                  Originally posted by wildirish317 View Post
                  If you can open the family by itself in Revit, do so, and delete the offending parameter. Then load it into your project.

                  Your project has a shared parameter "Product Page URL" that has a URL type, and your family has a shared parameter of the same name, but different type.
                  Hey,

                  I'm also trying to get a family in our template and I et the following error:

                  The shared parameter "00000000-0000-0000-0000-000000000000" cannot be added with name "00_isq_hoogte_min_2" and type "Length" because it conflicts with the existing name "REX.Content.Identity.RebarHooks" and type "Text".

                  Strange thing is that I can't find the "00_isq_hoogte_min_2" parameter in the family nor can I find the "REX.Content.Identity.RebarHooks" in our template. Even if I'd delete all parameters from the family it still gives the error. Any idea's?

                  Regards Rien

                  Comment


                    #10
                    Sometimes there is a conflict between parameters in families, and project parameters. Maybe check the project parameters to see if there is one with that name.

                    If not, the problem is likely that there is a parameter with a different "Name", but with a duplicate "GUID". This is especially likely since the GUID listed above is all zeros. There's probably more than one lame family creator, or buggy addin and they both inserted zeros.

                    Comment

                    Related Topics

                    Collapse

                    Working...
                    X