This is my current flow:
I am creating a flow to send SMS to multiple different recipients and I want to attach a picture with each of the SMS. The pictures are located in another folder in the same SharePoint site, but I am not sure how to do this based on their IDs. Can anyone provide some help with this problem?
Solved! Go to Solution.
Somehow I'm still getting error, even though the image's URL is correct.
Body:
{
"code": 21620,
"message": "Media urls: https://****.sharepoint.com/sites/*****/QR Codes/ATD3.png are invalid. Please use only valid http and https urls",
"more_info": "https://www.twilio.com/docs/errors/21620",
"status": 400
}
Headers:
{
"Twilio-Request-Id": "RQ68ef8765465747609997f1ad6863c4ed",
"Twilio-Request-Duration": "0.094",
"Access-Control-Allow-Origin": "*",
"Access-Control-Allow-Headers": "Accept,Authorization,Content-Type,If-Match,If-Modified-Since,If-None-Match,If-Unmodified-Since",
"Access-Control-Allow-Methods": "GET,POST,DELETE,OPTIONS",
"Access-Control-Expose-Headers": "ETag",
"Access-Control-Allow-Credentials": "true",
"X-Shenanigans": "none",
"X-Home-Region": "us1",
"X-API-Domain": "api.twilio.com",
"Strict-Transport-Security": "max-age=31536000",
"Timing-Allow-Origin": "*",
"x-ms-apihub-cached-response": "true",
"Date": "Tue, 06 Oct 2020 08:34:39 GMT",
"X-Powered-By": "AT-5000",
"Content-Length": "254",
"Content-Type": "application/json"
}
Hi @LanceP :
It's strange, I didn't encounter errors in my tests. Maybe you can try this solution (my test is OK):
Best Regards,
Bof
{
"error": {
"code": "notAllowed",
"message": "The feature has been disabled. Please contact your admin to get it enabled."
}
}
{
"Pragma": "no-cache",
"X-SharePointHealthScore": "0",
"SharePoint-CreateSharingLink-Error": "Sharing by link is not enabled on the web,site,or tenant.",
"X-SP-SERVERSTATE": "ReadOnly=0",
"ODATA-VERSION": "4.0",
"SPClientServiceRequestDuration": "204",
"SPRequestGuid": "40711da5-7b31-495a-9222-51980c2a508a",
"request-id": "40711da5-7b31-495a-9222-51980c2a508a",
"MS-CV": "pR1xQDF7WkmSIlGYDCpQig.0",
"Strict-Transport-Security": "max-age=31536000",
"X-FRAME-OPTIONS": "SAMEORIGIN",
"Content-Security-Policy": "frame-ancestors 'self' teams.microsoft.com *.teams.microsoft.com *.skype.com *.teams.microsoft.us local.teams.office.com *.powerapps.com *.yammer.com *.officeapps.live.com *.stream.azure-test.net *.microsoftstream.com;",
"MicrosoftSharePointTeamServices": "16.0.0.20523",
"X-Content-Type-Options": "nosniff",
"X-MS-InvokeApp": "1; RequireReadOnly",
"Timing-Allow-Origin": "*",
"x-ms-apihub-cached-response": "true",
"Connection": "close",
"Cache-Control": "no-cache",
"Date": "Tue, 06 Oct 2020 09:02:44 GMT",
"P3P": "CP=\"ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI\"",
"X-AspNet-Version": "4.0.30319",
"X-Powered-By": "ASP.NET",
"Content-Length": "144",
"Content-Type": "application/json",
"Expires": "-1"
}
So I guess my company has disabled the option to share any SharePoint images to 3rd parties?
Hi @LanceP :
Please try to set Link scope to "People in your organization" and try again.
Best Regards,
Bof
Ok, now the flow managed to run without errors, but in Twilio the SMS didn't actually get sent, and this is what I get in the Debugger:
Hi @LanceP .
you can check the below-mentioned URL.
That issue seems Twilio side. you can try the Twilio Debugger to test your Twilo /Code /Account.
Hope to help you to resolve your issue.
Hi @LanceP :
I tried many methods. So far, although flow can run normally, Twilio does not seem to support ‘Full Path’ and ‘Share Link’.
At present, I have not found a good way to support your needs. If you want, you can use email instead of SMS.
Best Regards,
Bof
Hi @v-bofeng-msft ,
Thanks for the effort you've put in for this problem, appreciate it.
I believe what you said is quite true, so I will have to look for another workaround then. So far I've thought of just placing the image's URL into SMS instead, for the E-mail part I've already sorted it out before this SMS issue.
Thank you again.
User | Count |
---|---|
180 | |
114 | |
88 | |
44 | |
42 |
User | Count |
---|---|
226 | |
113 | |
112 | |
69 | |
67 |