Hi, how are y'all doing?
I'm currently facing a challenging issue related to document renaming in a Portal environment using an S3 integration, and I would really appreciate any guidance or suggestions from the community.
Context
I'm trying to rename a document using the "Edit Document Properties" smart service inside a Portal, but the behavior is inconsistent depending on the environment and the file name used.
Problem Description
The issue is that I cannot use the "Edit Document Properties" smart service directly in a Portal, so I've been trying to work around this by calling an integration through a WebAPI. The WebAPI and the integration themselves work correctly, however, the S3 integration does not recognize the new name when it contains spaces or special characters.
What makes this even more confusing is that on a regular Interface, the rename works fine regardless of whether the file name contains spaces, special characters, or any other improper naming conventions. On the Portal side, it only works when the file name is considered proper, meaning it has no spaces, no special characters, and follows a clean naming pattern. As soon as the file name contains any of those elements, the S3 integration simply fails to recognize it.
What I've Already Tried
I tried changing the document name through an expression rule before passing it to the integration, attempting to sanitize it beforehand, but it did not work. I also tried setting the fileNames parameter directly on the S3 integration node, but the result was the same.
fileNames
Questions
Is there a known limitation with S3 integrations in Appian Portals when document names contain spaces or special characters?
Is there a recommended way to sanitize or encode file names before sending them to the S3 integration so it recognizes the new name properly?
Is the WebAPI approach the correct way to handle "Edit Document Properties" in a Portal, or is there a better alternative?
Thank you all in advance for your time and support!
With Special Character on file name during upload:
Without Special Character on file name during upload:
even though it says "error", when I get the link, it's possible to download when it returns the link (Without Special Character)
Discussion posts and replies are publicly visible
This is my integration calling my Web API