Hello,
I would like to use the hyperlink function to directly open a document on my network.
However, I am encountering an issue: ProjeQtOr seems to modify the link when opening it. For example:The link added to my item:
N:ProductionDxxxxxx_Documents Applicablesxxxxxx.pdf
The link opened in my browser when I click:
n/Production/D/xxx/xxx/_Documents%20Applicables/ xxxxxx.pdf
Do you have a workaround for this issue, or is it a bug in the tool?
Even simpler: is it possible to open a PDF document from my network in the Projeqtor viewer?Thank you for your feedback.
Have a great day.
Hello
I can't answer this address hijacking but I have warned the "computer engineers" of this problem and should get back to you soon.
On the other hand, for...
Even simpler: is it possible to open a PDF document from my network in the Projeqtor viewer?
If you open outside the application, the document will be opened by the browser (in general) or by the application that hosts it, on the other hand, if it is in the ProjeQtOr attached files, simply click on the PDF icon and the viewer opens directly in the application to display it.
Hello,
Do you have any updates on this matter?
Opening PDF documents from my network doesn't seem to be working. The link that opens in the browser doesn't match the one provided.
N: --> N
Thanks for your feedback
Hyperlink won't work if file name includes chararters that cannot be contained is a URL or URI.
And scpace is one of these characters...
Moreover hyperlink with locally mounted drive to N: will work only for users who have same drive mounted on exactly same location.
Hi,
Thanks for your feedback,
You're absolutely right — using a local drive like N: assumes all users have the same drive mounted at the same path. but this is the case, no problème.
Regarding special characters in file names,
A simple workaround is to URL-encode the link, replacing invalid characters with their encoded equivalents, maybe an option activatable, for use a script for this ?
Regards,
A simple workaround is to URL-encode the link, replacing invalid characters with their encoded equivalents, maybe an option activatable, for use a script for this ?
It is already what is done, and it's why it does not work for locale files : it works for real web access but not for local.
Thank you for your feedback. I appreciate the clarification. Given the current limitations with local files, would you happen to have any suggestions or possible workarounds to address this issue?
Hi,
As this feature was not designed to access local files, only workaround is to acces only files with names formatted so that urlEncode does not change the name.
So for instance, only use alpanumeric characters and dot (point) no other.
Thanks for your feedback,
Have a nice day