google_slide_viewer

Presentations tend to live outside the ERP, and linking to them means sending the user away. For content that is meant to be read in context, a course slide deck, an onboarding presentation, a product briefing, an embedded preview is worth more than a link.

This widget does that for Google Slides specifically. It takes the URL stored in a text field, recognizes the Google Docs form of it, and rewrites it into the address that renders a preview, which it then frames on the form.

It also understands that a deck has pages. If the record carries a companion field with the page number, the preview opens at that slide rather than at the first one, which makes it usable for referencing a specific point in a deck.

Embedding rather than linking is the difference between a resource people consult and one they mean to consult later. On training and course records especially, keeping the material on the same screen as the metadata about it is the whole point of managing it in Odoo at all.

The constraint to note is that only Google Docs links work. Any other host, including other Google products, produces no embed, and the field silently shows nothing. If your content lives elsewhere, this widget is not the route, and a link or a stored PDF is.

The usual usage

<field name="slide_url"
       widget="google_slide_viewer"/>

A Google Docs link in the field renders as an embedded deck starting at the first slide.

With a starting page

<field name="slide_url_page" invisible="1"/>
<field name="slide_url" widget="google_slide_viewer"/>

The companion field's name is the main field's name plus a page suffix, which is how the widget finds it.

A link that will not embed

# no embed: not a Google Docs URL
https://example.com/deck.pdf

The regular expression matches Google Docs addresses only; anything else produces no embed and no error.

The URL rewriting is a single regular expression. It matches an address beginning with the Google Docs host and captures both the path marker, which differs between a published link and a direct document link, and the document identifier. Those two pieces are recombined into a preview address with the slide number appended.

That means both common shapes of Google link work, and everything else fails closed: no match, no URL, nothing rendered.

Two leftovers are visible in the source and worth recording. The URL getter starts by reading a legacy value property that Odoo removed from field props several versions ago, so that first read always yields nothing before being overwritten by the real lookup. And the failure notification refers to a spreadsheet rather than a presentation, which is a clear sign the widget was adapted from a sibling and the message was not updated.

The page lookup is the other detail. It reads a field whose name it constructs by appending a page suffix to its own field name, falling back to the first slide when that field is absent or empty. Being a convention rather than an option, it is easy to miss when reusing the widget.

Odoo 20 is expected at Odoo Experience in Brussels, 24 to 26 September 2026. The development branch is unstable and this may still change; we re-verify this page after the release.

Byte-identical. The file on the development branch matches Odoo 19 exactly, including the legacy read and the mismatched failure message.