Do file attachments work?

[Piedone]

I also tried to write a (HipChat to) Teams migration utility (https://github.com/Lombiq/HipChat-to-Microsoft-Teams-Migration-Utility) but I couldn't get attachments working. Apparently this is not possible via the API, despite it appearing as being working: https://techcommunity.microsoft.com/t5/Microsoft-Teams/Graph-API-Issues-while-creating-new-chat-thread/m-p/242558

Do posting file attachments to Teams messages still work for you?

Thank you!

[tamhinsf]

Slack attachments are uploaded into the Sharepoint folder associated with the Team and Channel, and the message itself is written to reference the attachment in Sharepoint via URL. Long story short - attachments aren't "attached" per se.

[Piedone]

I see, thanks.

[Piedone]

Also Tam, I see you're a Microsoft Technical Evangelist. Could you make the Teams team aware, that for us to be able to build a full-fledged HipChat to Teams migration app the Teams API needs to be improved? If you check out the GH page I linked you'll see that all open issues require something from the API which is lacking today.

This is getting extremely urgent since HipChat is closing down by 15 February, so until then, and only until then is the time to move users over from there. We did what we could but now we're hitting walls that we can get around using messier and messier workarounds.

If you could connect me with the relevant people that would be awesome too (zoltan dot lehoczky at lombiq dot com).

[essgit]

Hello,

Attachments do not seem to work

In the documentation, it says: On channelsurf/fileattachments folder. You'll then see subfolders whose name maps to the file attachment's unique ID on Slack. Open a subfolder, and you'll have access to the actual file attachment.

I don’t see file attachments at all

Picture of no files:

Output from CMD:

Create web pages that show the message history for each re-created Slack channel? (y|n): y
Copy files attached to Slack messages to Microsoft Teams? (y|n): y
Scanning users in Slack archive
Scanning users in Slack archive - done
Scanning messages in Slack channels
Migrating messages in channel general
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-01.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-04.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-05.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-06.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-07.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-08.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-09.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-10.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-11.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-12.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-13.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-14.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-15.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-16.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-17.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-18.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-19.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-20.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-21.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-22.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-23.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-25.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-26.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-02-27.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-01.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-02.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-03.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-04.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-05.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-06.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-07.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-08.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-10.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-11.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-12.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-13.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-14.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-15.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-16.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-17.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-18.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-19.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-20.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-21.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-22.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-25.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-26.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-27.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-28.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-29.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-03-30.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-04-01.json
File C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\2019-04-02.json
Trying to upload file to MS Teams SPo Folder C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\0.json
Upload of attachment to MS Teams completed /general/channelsurf/messages/json/0.json
SPo ID is 01LSRDC74AZWVG67OFWZFLDXZ7C2LDLZVC
Trying to upload file to MS Teams SPo Folder C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\1.json
Upload of attachment to MS Teams completed /general/channelsurf/messages/json/1.json
SPo ID is 01LSRDC75IRLEZDZSARJA3KNYFI5Y3TE67
Trying to upload file to MS Teams SPo Folder C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\0.html
Upload of attachment to MS Teams completed /general/channelsurf/messages/html/0.html
SPo ID is 01LSRDC75NGXIQEVRIBRGIV6CY6ZA3HBDK
Trying to upload file to MS Teams SPo Folder C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp\general\1.html
Upload of attachment to MS Teams completed /general/channelsurf/messages/html/1.html
SPo ID is 01LSRDC74XVVT5OZ2J3RCIHXH7QFJMHF6F
Scanning messages in Slack channels - done
Tasks complete.  Press any key to exit

Cleaning up Slack archive temp directories and files
Deleted C:\Users\essuser\AppData\Local\Temp\tmpE328.tmp and subdirectories

C:\Users\essuser\source\repos\ChannelSurf-master\ChannelSurfCli>

[alextanti]

A year later ... did anyone manage to migrate attachments?

[essgit]

I don't think so

Get Outlook for Androidhttps://aka.ms/ghei36

---

From: Alex Tanti notifications@github.com Sent: Wednesday, April 22, 2020 9:16:11 AM To: tamhinsf/ChannelSurf ChannelSurf@noreply.github.com Cc: Michael Besko michael.besko@fareportal.com; Comment comment@noreply.github.com Subject: Re: [tamhinsf/ChannelSurf] Do file attachments work? (#14)

A year later ... did anyone managed to migrate attachments?

— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_tamhinsf_ChannelSurf_issues_14-23issuecomment-2D617772478&d=DwMCaQ&c=iBlh5sfyJetM3CZrWQ7qPRSW4DDbeEqhetx-pU5sAiQ&r=zCdm5ISd2_wxm4zzVAZF5kRAn2UNijjrbgwWYkY5Oz0&m=ziBVEiyBgCgdBjFvALywiR05s-3P2UpPCdiLLo9XCsw&s=sdspCFC1UolCMnmx6yS5sCeQETbpfAmNmwK-amqahcY&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ALYBMXBCPHZK6EWMYJN6TODRN3UZXANCNFSM4GON3AZA&d=DwMCaQ&c=iBlh5sfyJetM3CZrWQ7qPRSW4DDbeEqhetx-pU5sAiQ&r=zCdm5ISd2_wxm4zzVAZF5kRAn2UNijjrbgwWYkY5Oz0&m=ziBVEiyBgCgdBjFvALywiR05s-3P2UpPCdiLLo9XCsw&s=0L2BWqpxrw27jLo0sQkOvIRinzR0f4Q7Ftjga-w7XHE&e=.

Disclaimer: The information in this email and any attachments may contain proprietary and confidential information that is intended for the addressee(s) only. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, retention or use of the contents of this information is prohibited. When addressed to our clients or vendors, any information contained in this e-mail or any attachments is subject to the terms and conditions in any governing contract. If you have received this e-mail in error, please immediately contact the sender and delete the e-mail.