Status Update
Comments
bl...@google.com <bl...@google.com> #2
ky...@gmail.com <ky...@gmail.com> #3
"We make the copies so our customers can generate multiple reports in quick succession without having any race condition issues, but the warning is blocking us from successfully pulling the data through the ImportXML function."
gh...@gmail.com <gh...@gmail.com> #4
br...@sitesusa.com <br...@sitesusa.com> #5
Same issue for us, we use the =IMAGE(url) to allow a logo to appear for our clients. Now all images are now showing up in finished sheets or exported PDF with "#REF" error because it is requiring "Allow Access" to be clicked, which is not possible.
I know in the App Scripts .js library you can create a CellImage, but not seeing any of that similar functionality in the .NET package(s). Any update would be great!
ge...@gmail.com <ge...@gmail.com> #6
ky...@gmail.com <ky...@gmail.com> #7
ja...@gmail.com <ja...@gmail.com> #8
Is there any way in the Java library google-api-services-sheets to set consent to insert an image into a Google spreadsheet using the =IMAGE() formula?
I am asking for a quick solution as this is a production version of the software because the change was made without prior information or warning and I was not able to prepare any alternative solution.
l0...@gmail.com <l0...@gmail.com> #9
ol...@addonsforgapps.com <ol...@addonsforgapps.com> #10
This impacts our workflow significantly because we use Google Spreadsheet files as an intermediate step to automatically generate PDF files. If a Google Spreadsheet file contains a #REF error, this error is also reflected in the PDF, thereby breaking our automation process.
fo...@kolom.net <fo...@kolom.net> #11
Teachers are filling in a Google Form and uploading a photo from a pupil that´s located on the drive and that form will be converted to a spreadsheet template and that will be converted to a PDF document (via Form Publisher plugin). Because of the new warning, we are not able to see photo´s in the PDF file (#REF!).
jp...@google.com <jp...@google.com> #12
I have forwarded this issue to the engineering team.
re...@gmail.com <re...@gmail.com> #13
I ran into this same issue. We use Google Sheets -> PDF to generate production worksheets and labels with QR Codes. The QR Code images are generated via a website we control and embedded via an IMAGE()
hyperlink. We never open the raw Google Sheet, just use it as a means of formatting the labels for print via PDF. Since manual user intervention is required, it broke our production process - all the QR codes were replaced by a #REF
error.
I did find a workaround which worked very well, based on this blog:
We were previously building an IMAGE()
link, like this:
someRange.setValue("IMAGE(\"" + url + "\")")
Instead, we build an inline image like this:
let image = SpreadsheetApp
.newCellImage()
.setSourceUrl(url)
.build();
someRange.setValue(image);
This replaces the IMAGE()
link with an embedded, inline image that fits in the exact same cell that the IMAGE()
hyperlink previously fit into. I didn't have to change any layout at all, it just worked.
This will obviously not solve the problem for people using the IMPORTXML()
function, but is a handy workaround for embedded images.
sa...@gmail.com <sa...@gmail.com> #14
cl...@gmail.com <cl...@gmail.com> #15
Please provide an API to accept external URLs programmatically.
fo...@parauco.com <fo...@parauco.com> #16
cl...@betterreports.com <cl...@betterreports.com> #17
We finally found a work around which involves calling an undocumented endpoint to approve the external url access programmatically.
Simply issue an http POST to the following url:
This basically mimics the user approving external urls.
However, we are uncomfortable using an undocumented API which will probably break under us again in the future.
Google Sheets team, please understand that many apps have a dependency Google Sheets. If you are going to make breaking changes, please let the community know in advance and increase the major version of the API so that we can reliably manage upgrades.
vi...@gmail.com <vi...@gmail.com> #19
affected my work.
qu...@alumo.co.za <qu...@alumo.co.za> #20
pd...@gmail.com <pd...@gmail.com> #21
cl...@betterreports.com <cl...@betterreports.com> #22
Hi Google, Can you give an update on the situation? Is a new official API endpoint in the works to programmatically allow external url?
cl...@betterreports.com <cl...@betterreports.com> #23
It's been a month since the API broke under us and still no words from Google?! Google, do you even care that you break the apps created by your partners?
mf...@google.com <mf...@google.com> #24
Michael from the Sheets team here.
We are working on adding options to the Google Sheets API and the Apps Script Sheets integration to support acknowledging the import warning on a per-document basis (essentially mimicking the user flow, although it can be done in advance of adding any IMPORT-related formulas).
We expect this to rollout in the next few weeks. I will provide an update once it's ready for use.
cl...@betterreports.com <cl...@betterreports.com> #25
Thank you Michael for your update 👍 In the future, please give the sheets dev community a warning and version the API when you introduce breaking changes so that we can prepare accordingly and not have our apps break suddenly.
ci...@gmail.com <ci...@gmail.com> #26
In the meantime, the workaround at #18 fixed the issue for all IMPORTDATA, IMPORTRANGE and all, IMAGE included.
cl...@betterreports.com <cl...@betterreports.com> #27
@sheets-team, please don't break the work around above until the official API is available.
ju...@daaily.com <ju...@daaily.com> #28
pa...@muchgroup.co.uk <pa...@muchgroup.co.uk> #29
pa...@muchgroup.co.uk <pa...@muchgroup.co.uk> #30
mf...@google.com <mf...@google.com> #31
This has now been rolled out to the
SpreadsheetProperties
{
"importFunctionsExternalUrlAccessAllowed": boolean
}
Whether to allow external URL access for image and import functions. Read only when true. When false, you can set to true.
cl...@betterreports.com <cl...@betterreports.com> #32
Thank you, that fixes the issue for us.
du...@gmail.com <du...@gmail.com> #33
Can someone please explain step by step what we need to do to apply the below solution? Do we have to set "importFunctionsExternalUrlAccessAllowed": true in spreadsheet properties and that would be all? Thanks!
cl...@betterreports.com <cl...@betterreports.com> #34
Yes, that's all you have to do.
Description
Description
I work on an app that integrates with Google Drive and Google Sheets to create PDF reports from Google Sheets using the ImportXML function (as well as the Image function). Starting on February 7th we started receiving reports of blank PDFs getting generated. After digging into it, I'm seeing the following warning on the affected sheets:
Warning: Some formulas are trying to send and receive data from external parties.
We use the .NET
Google.Apis.Drive.v2
nuget package to make copies of the original Google Sheet and insert the IMPORTXML function so the rest of our logic can create the PDF reports. We make the copies so our customers can generate multiple reports in quick succession without having any race condition issues, but the warning is blocking us fromAre there any work arounds for this or is there anything that can be done on the .NET side using the Google SDK to automatically allow access to external parties? We're seeing a steady increase in reports from clients, but haven't been able to find any way around this issue.
Output
No data is imported into the sheet until hitting Allow Access in the warning message.
Steps
=image("https://wallpaperaccess.com/full/4958480.jpg")
References to other users experiencing the same issue