Hi All,
For context, our organization is running version 2024.2.1.14.
My current application creates a report via the the Render tool (configuration settings below), and then the report is included as an attachment within an E-mail tool. When executed within Designer, the results appear as expected. A new report is saved within the referenced folder, and the same report is received via e-mail. This also occurs when executing manually within the gallery.
When I execute the workflow via API, I receive the e-mail I would expect, with the updated report; however, the new report is not saved within the referenced folder. It would appear it is only creating a temporary report in this case.
Any clue why this might be occurring? The API response does not indicate any errors.
Thanks in advance.
@Noah-Waite When you saved the workflow up to the server, did you click manage workflow assets and make sure the file path for the output file was deselected?
If you leave it check when saving, it will include the file in the packaged file up to the server. If you leave it unchecked, it will keep the referenced file path.
This means 2 things: Your server has to have access to the file path you are trying to write to, AND you must have the UNC path defined for the output so the server knows exactly where to look
Helpful Links:
https://knowledge.alteryx.com/index/s/article/Assets-and-Packaging-Workflows-1583460636757
Bacon
Where to Change to UNC Path
Setting to UNC Path
Where to get to Workflow Assets
Deselect the desired file path