You are viewing limited content. For full access, please sign in.

Question

Question

Embedding a google doc in a Form [Cloud], unable to save the Form to the repo

asked on April 25

I have a Laserfiche Cloud form that has an embedded goggle doc in an iframe. Its a 20 page policy document. The google doc displays fine and the form submits without issue, but when I save to the repository the task fails with 
 

Failed to generate a document from the form: Error:  {"stack":"TypeError: Cannot read properties of null (reading 'context')\n    at Wfc (https://www.gstatic.com/_/apps-fileview/_/js/k=apps-.....

Is this a limitation of the google doc (I can try hosting it somewhere else). Or does laserfiche not know what to do with the embedded doc when it saves it to repo?

0 0

Answer

SELECTED ANSWER
replied on April 28

You could use field rules to hide the custom html element hosting the iframe when the process step or stage contains your print step

1 0

Replies

replied on April 28

I'm wondering why you need to save a 20-page document in a form? Typical use cases hide iframes on print as they are not required to be printed. Also, the entirety of the documents contents are likely not rendered in the iframe anyway so I'm not sure what is intended to be printed here.

Either way, the error is on google's end. Are you instantiating the iframe with JavaScript? It looks like the script is being initiated before a component is ready/available on the DOM.

0 0
replied on April 28

I don't want to save the embedded doc at all. I have the 20 page doc in an iframe and the save to repo task failed at the "Wfc" url above. I am just embedding the google doc in an iframe in a modern form. 

If this is on google's end I wonder if I should try and host the doc on a public website and not shared through google drive. 

0 0
SELECTED ANSWER
replied on April 28

You could use field rules to hide the custom html element hosting the iframe when the process step or stage contains your print step

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.