Workspace to FTP | Community
Skip to main content
New Participant
August 10, 2018
Investigating

Workspace to FTP

  • August 10, 2018
  • 13 replies
  • 13017 views

If Ad Hoc is going to die then Workspace needs to be an acceptable replacement. It is already better in many ways, but not good enough.

I hear 50,000 rows is coming. Good.

But we NEED the ability to send via FTP (and sFTP). We cannot stop using Ad Hoc until this happens (workbench is not an option for a lot of segments).

13 replies

New Participant
July 14, 2022

We need this ftp functionality too. With the removal of Scheduled Reports, we will lose this feature.

New Participant
June 2, 2022

@jenla5 Is the Workspace to FTP option still under review or planned? We're interested in this too as we're running into issues with scheduled projects suddenly not sending, sending again (without any changes), and others not sending. Any other options that don't rely on email and email queue finickiness would be ideal. Thanks!

New Participant
February 7, 2022

What's the status of this request @jenla5? Our stakeholders continue to ask.

New Participant
October 14, 2021

It's been over 3 years since the first comment on this. @jenla5, is this still marked Under Review, as it was over two years back?

New Participant
September 21, 2021

So ... any update on adding SFTP capability for Analysis workspace ?  😁

New Participant
March 1, 2021

Any update on adding FTP capability for Analysis workspace ?

Employee
October 8, 2019

This is something we are actively researching, I will be able to share more of an update in the spring. Thank you for sharing your use case for FTP/SFTP delivery!

New Participant
October 8, 2019

FTP also is needed in our case because we have a system that cannot accept the published emails out of the workspace area. So our users cannot share artifacts through the 'share/ send file' functionality of the tool. FTP would give us a needed option of getting info out of the Adobe walls and to us....

Why? combination of a limitation of our system and the limitations of Workspace publish options.

  • Outbound email from Adobe’s Adobe Analytics Workspace publishing process arrive to us as completely HTML
  • oddly enough, we have a system which can only accept emails that are of a multipart type (that contain both html and plain components). So, our users of Workspace cannot send to the users of that receiving email system
  • There is no configuration within the Workspace publishing infrastructure (whether that be select-able by user or configurable by Adobe folks who operate the system supporting the Workspace publish process --- per info discovered Incident: 190911-000461) to change the HTML to a multipart type.
  • FTP would be an option of getting these reports into our walls which we could then move out to users with needed message formatting.

jen.lasser​ does this feature have any chance of making it any time soon?

New Participant
September 9, 2019

Thanks for your reply Jen! One of our Company’s use cases would be utilizing SFTP delivery to automate Workspace dashboards and auto publish them up onto our company’s internal exchange website. Standard email delivery is not supported for this effort. I could envision Amazon S3 and other delivery destinations being valuable for Workspace as well. As our company’s data science team heavily relies on Amazon S3. Our web analysts spend lots of time and effort making Workspace reports for the company. Having the ability to share and deliver Workspace reports out via modern delivery methods would only enhance Workspace’s value proposition and save time in having to replicate these reports out in other tools.

Impact on not offering FTP/SFTP would be that our inhouse data processing warehouses would not be able to receive direct STFTP/FTP from Adobe. Rather having to rely on raw formats from data warehouse etc. As Adhoc Analysis already offers FTP, if it were to sunset without Workspace being able to offer the same functionally we would have to re-engineer multiple reporting streams.    

Employee
September 9, 2019

It is currently marked Under Review and is on our backlog for consideration. We have a few questions for the thread that will help us determine the right solution. Please respond inline or feel free to message me directly:

- What are your primary reasons/use cases for needing FTP?

- Do you have security concerns with FTP? Do we need to offer SFTP?

- Are other delivery destinations (Amazon S3, Azure Blob) that need to be supported?

- If only Amazon S3 and Azure Blob were supported (not FTP), what would be the impact to your process?

Please let us know!