Better relative path support for URL Parameters

[cyril]

Currently it is pretty cumbersome to add relative path to an url parameter, you have to /[Model Folder]/[Sub-Folder]/[FileName and extension].

1. Why do we need to write the current [Model Folder]. If the folder is renamed, links don't work anymore. Common relative path use file location and don't need this.
2. When you work on a central model relative path is made from your local file path. It would be better to consider it as relative from central file path.
3. It would be nice that it handles previous folder as usual relative path.
   Example :
   Central file path : CaseFolder/RevitProject/0000_ProjectName_R17.rvt
   Linked file path : CaseFolder/Documentation/xyz.pdf
   Relative path : ../Documentation/xyz.pdf

[sarsenault2CCSS]

The way I see it, you should have two libraries. One central library on the network that never changes name or anything. Everything else should be further up the chain PAST the Revit file or even inside the Revit file itself.

/CENTRAL LIBRARY  <<< this is all your firm's families, materials, standards on the network

/Project folder/Revit   <<<model goes here, this is project specific folder

/Project folder/Revit/families

/Project folder/Revit/custom materials

/Project filder/Revit   <<<everything custom to the project should go past this point, including CAD and Revit links

With that being said, Autodesk needs to fix their E-transmit tool so that it pulls the material images and other important elements from the network directory to the local Revit project directory for proper archival and transmittal.