we’re using AF Utilities “Write to Excel Template” node from @AnotherFraudUser to write some data to some heavily formatted excel files that our users want to keep the way they are.
Our problem is that when the output file path is set to “Relative” it looks like the node adds a prefix to the value that we set, specifically “\<flow name>\”, thus making the path invalid.
Attached is a sample workflow that copies a template file from the input data folder (also attached) to a temp directory and then tries to create a new output file in:
1- the source folder where the template is initially stored (relative path)
2- the temp folder (relative path)
3- the temp fodler (absolute path dynamically generated)
Number 3 is the only one that works, but that’s not applicable when the flow gets published on server.
Has anyone else experienced the same issue? Is there a workaround?
Thanks in advance