You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I navigate the value link, the filename of the download is changed to File1.txt (probably combination of idShort and mimeType)
There are many flaws:
the content of "File1.value" may change anytime and cannot be cached
the actual filename of the download may change anytime (or get lost compared to AASX files) and we need business-logic to workaround it
I understand that this is not at all specified in AAS specs, ideally you would just replace the static file "basyx-temp/aasx1/files/aasx/files/abc.txt" on file upload in case the file was coming out of the AASX file.
The text was updated successfully, but these errors were encountered:
Hi all,
my scenario is to load an AASX package with a File element "File1" which references a file which is included in the AASX package "abc.txt":
after the load of the AASX file into the server, a file element is created
When I navigate the value link, the filename of the download abc.txt (probably taken from AASX file)
After upload the file by using /File1/upload URK, the content is changed to:
When I navigate the value link, the filename of the download is changed to File1.txt (probably combination of idShort and mimeType)
There are many flaws:
I understand that this is not at all specified in AAS specs, ideally you would just replace the static file "basyx-temp/aasx1/files/aasx/files/abc.txt" on file upload in case the file was coming out of the AASX file.
The text was updated successfully, but these errors were encountered: