IssueTracker

Hello, thanks for your report.

Unfortunately, I could not reproduce the issue. Inside the for loop, does the line var body = targetDoc.getBody(); always return this error? Or does it fail after several loop runs? Can you reproduce this with another Script?

Thanks

Hi, thank you for the answer. It always returns the error for me.

Attached is a quick video of what happens when I run the program.

Additionally, after checking my app script dashboard, and looking at failed executions, I came across one of these errors:

Exception: You do not have permission to call DocumentApp.create. Required permissions: https://www.googleapis.com/auth/documents

Yet, the scopes of the script already include that permission (screenshot attached)

I'm stumped. Is there anything else I should provide?

Thanks for the quick reply.

Make sure you have reading or editing permissions, and check if the Document is in the Drive's Trash. If this is not the case, create a new Document and try with the new Id. Regarding the Scopes issue, go to myaccount.google.com/permissions, remove the App's permissions and run the Script again. See if that fixes the issue.

Cheers!

The script creates a new document every time, so it just pops up in my drive. The document is never in the trash, until I delete it.

For the scopes issue, I tried removing the App's permission, and re-adding it by running the script again, but nothing changed.

I even copied every part of the script into a new document, and when running it again, the same exact error shows up...

Anything else I could try?

Thank you!!

Actually, I think I just fixed the problem, but I have come across a strange issue.

Basically, I had a footnote in my google document. For some reason, having a footnote in the document causes that error to pop up.

After removing any footnotes (such as the screenshot shown below), everything is fine, and the document copies over.

Any idea as to why this may be happening?

Thanks!!

Thanks for the information! I'm glad you found a workaround. I tried to reproduce the issue using a Document with footnotes but it worked as expected. Would you mind sharing an example of the Document, and a minimal reproducible example of the Script?

Thanks!

This is the script I am using:

function speechDoc() {
  var currentDoc = DocumentApp.getActiveDocument().getBody();
  var targetDoc = DocumentApp.create('Speech Doc');
  var totalElements = currentDoc.getNumChildren();

  for( var index = 0; index < totalElements; ++index ) {
    var body = targetDoc.getBody();
    var element = currentDoc.getChild(index).copy();
    var type = element.getType();
    
    //Goes through each type of element
    if( type == DocumentApp.ElementType.PARAGRAPH ){
      body.appendParagraph(element);
    }
    else if( type == DocumentApp.ElementType.TABLE){
      body.appendTable(element);
    }
    else if( type == DocumentApp.ElementType.LIST_ITEM){
      body.appendListItem(element);
    }
    else if( type == DocumentApp.ElementType.INLINE_IMAGE ){
      body.appendImage(element);
    }
    else if( type == DocumentApp.ElementType.HORIZONTAL_RULE ){
      body.appendHorizontalRule();
    }
    else if( type == DocumentApp.ElementType.PAGE_BREAK ){
      body.appendPageBreak();
    } 
    else {

    }
  }
}

For some reason, whenever there is a footnote in the document, the script is unable to copy it over to another doc. To replicate what I'm doing, you can try using this document: https://docs.google.com/document/d/1-EVYelCmNNiuGueaYTcEnWfm_0m7SIiAEkSU4xh10u4/edit?usp=drive_web (Footnote Copy Test)

The script works with images, and basically everything else I put in my document.

It is possible that when running through each type of element (paragraph, table, list item, inline image, horizontal rule, and page break), it isn't able to recognize a footnote and just crashes? How can I have the program not crash when there's a footnote in the document?

I also wouldn't mind if the program was able to copy everything BUT the footnote... but for some reason it just crashes and doesn't copy anything over which is a concern I have for my project

Hello, sorry for the late reply. I can confirm I could reproduce the issue, so I reported it to the appropriate team. As a workaround, you could implement a try catch so this error doesn't interrumpt the process.

Thanks for your collaboration!

Thanks!!

Hello Mathew,

Try adding targetDoc.saveAndClose() after the for loop. It should save the target document will all the copied elements.

function speechDoc() {
  var currentDoc = DocumentApp.getActiveDocument().getBody();
  var targetDoc = DocumentApp.create('Speech Doc');
  var totalElements = currentDoc.getNumChildren();

  for( var index = 0; index < totalElements; ++index ) {
    var body = targetDoc.getBody();
    var element = currentDoc.getChild(index).copy();
    var type = element.getType();

    //Goes through each type of element and moves it to the new document titled 'Speech Doc'
    if( type == DocumentApp.ElementType.PARAGRAPH ){
      body.appendParagraph(element);
    }
    else if( type == DocumentApp.ElementType.TABLE){
      body.appendTable(element);
      }
    else if( type == DocumentApp.ElementType.LIST_ITEM){
      body.appendListItem(element);
      }
    else if( type == DocumentApp.ElementType.BOOKMARK ){
      body.appendBookmark(element);
    }
   
    }
  targetDoc.saveAndClose();
}

Hello,

Unfortunately, after adding that line of code, the same error shows up (when trying to transfer a footnote)

Exception: Service Documents failed while accessing document with id 1y2m7i9qgFWdvWBahrWcwmJxBn91p-dcc9eccPMcyrF0.
    at speechDoc(myProject:65:13)

Except now it points to line 65, which is the saveAndClose line that I just added.

function myFunction() {
  var sheet = SpreadsheetApp.getActiveSheet();

  var charts = sheet.getCharts()[0];
  Logger.log(sheet.getCharts()[0])
  var chart = charts.modify()
    .setOption('title', "updated")
    .build()
  sheet.updateChart(chart);
  }

Same issue.

Please see the correct issue for this, https://issuetracker.google.com/305838577, which is related to general reliability in saving a document. I'm going to lock this issue for now as it is much more specific about footnotes.