0 Members and 1 Guest are viewing this topic.
I used that Dynamo script to reveal the fact that the Configuration path was missing. I have handled the GUID issue before successfully. Since the Configuration path is still in the Revit model it will update the GUID. Since the Configuration path is not in the Revit model I am working with, it does not know where to look to do anything with it. Please see the images in the post above that show a comparison of the results from the Dynamo script. One side shows the Configuration path in a Revit model and the other shows that same field blank in another. The blank field is the situation I am dealing with here.
Does the dynamo script report the GUID?
Looks like it does for other projects, but not this particular one.
Quote from: shilgartner on May 13, 2025, 13:43:47 PMI used that Dynamo script to reveal the fact that the Configuration path was missing. I have handled the GUID issue before successfully. Since the Configuration path is still in the Revit model it will update the GUID. Since the Configuration path is not in the Revit model I am working with, it does not know where to look to do anything with it. Please see the images in the post above that show a comparison of the results from the Dynamo script. One side shows the Configuration path in a Revit model and the other shows that same field blank in another. The blank field is the situation I am dealing with here.Been a while so anything's possible over time and the limited scenarios I've encountered so take that disclaimer for what it's worth but...To get a Revit model to see a Config when it's lost it, it needs 2 things...1) A GUID2) Value Config NameYou shouldn't need the path. The "Path" comes from the Registry entries that define the Configs for the version of products you're using. That "Registry Path" points to MAP.INI which then lists all the other paths a config needs. Use Dynamo to set both the GUID and Config Name and I think you'll be ok.