Announcing AppSheet smart chips for Google Docs!

Hello AppSheet Community,

As you may have seen already, we just launched AppSheet smart chips for Google Docs!

What are AppSheet smart chips?

Smart chips in Google Docs are already recognized as a powerful way to provide users rich, in-context views of linked assets and drive real-time decision making by bringing relevant data from places like Sheets, Slides, and Calendar directly into Docs. Meanwhile, AppSheet creators have been streamlining business processes and placing solutions directly into the hands of their users.

The release of AppSheet smart chips combine the power of smart chips’ in-context experience with the bespoke solutions built in AppSheet so that detail and deck views from any app can run directly from Google docs via a smart chip

AppSheet’s integration with smart chips lets users view and take action on the data in real time, including triggering automations–all without having to leave Docs.

Why is this valuable?

Consider a travel plan, trip report or budget request as an example. With AppSheet smart chips:

  • An AppSheet creator could insert a smart chip of all travel requests for a department in a Google Doc, thus enabling a streamlined approval flow and automation without requiring the approver to navigate through the approval app,
  • App users could also insert views of their pending or approved trip requests into a travel plan doc for stakeholders to easily review/take action.
  • Multiple chip-based views showing real-time information from several different apps could be inserted in a single document, transforming the Doc into a dashboard or hub for all trip related information and actions.

Essentially, any user can insert detail or deck views from apps that they have access to into Docs, and collaborators can see and take action on AppSheet data directly from the document.

Installing the “AppSheet for Google Docs” Add-On

To get started, install the AppSheet for Google Docs Add-On.

Inserting an AppSheet smart chip into your Google Doc

Once installed, you can immediately begin adding AppSheet smart chips to render application views in your Google Docs. Simply navigate to the user-facing view of a deployed app you’d like to include, copy the view URL, then paste it into your Google Doc.

Here’s step-by-step instructions for how to add AppSheet smart chips into your Google Docs.

  • Open an AppSheet app you wish to render in your Google Doc. You can add as a smart chip any AppSheet app you have access to, whether as a user or a creator. Note that once inserted as a smart chip, the app will still respect any policies or permissions configured in AppSheet. This means that you’ll need to share the app with any users who should have access to the data presented in the smart chip. For this example, we’ll use the Simple Inventory template app.
    cschalk_ws_2-1700247862810.png
  • After opening the app in the AppSheet editor, you’ll want to open the app in a new tab to obtain a full screen view of the app.
    Hint: Click the Open in tab option in the top corner of the editor.
    cschalk_ws_3-1700247862727.png

     


    This will allow you to extract the URL of the view you wish to insert into a doc.

  • After opening the app in full screen mode, navigate to the Inventory Log view In your browser and copy the full URL of the app view you wish to add to your Doc.

    cschalk_ws_4-1700247862658.png

     


    The URL will generally be of the form:
    https://www.appsheet.com/start/…#appName=[YourAppName]&view=[YourViewName]]

    Note: The full URL will typically contain other HTTP parameters including group, page, sort, table etc. The minimum parameters for smart chips to work are appName and view.

  • Once copied, paste the URL into your Google Doc in the position that you wish the view to appear.
    cschalk_ws_5-1700247862752.png
  • Then click [Tab] to replace the URL text with the smart chip.cschalk_ws_6-1700247862617.png
    Once inserted into your Doc, you’ll be able to hover or click on the chip to see the inserted AppSheet view. Once the chip renders, you’ll be able to interact with the view just as you would in the actual AppSheet application.
    • Note: Recall again that users of the chip in the Google Doc must already have access to the view in the application.
      cschalk_ws_7-1700247862807.png
  • Feel free to experiment with other views in your app!
    Remember that only deck and detail views will render in a smart chip.
    For example the ‘Levels’ view of the Simple Inventory app renders as:cschalk_ws_8-1700247862706.png

Availability
Available to Google Workspace customers with AppSheet licenses and AppSheet licenses.

Further Resources
Google Help: Use AppSheet smart chips in Google Docs
Google Workspace Marketplace: AppSheet for Google Docs

Let us know your use cases!
If you have any specific use cases in mind for using smart chips, feel free to share it and other feedback in this thread!

10 24 2,114
24 REPLIES 24

You should note that in order to point to a specific view you need to copy the deeplink to that view.
It can be found under Behavior

SkrOYC_0-1700261979671.png

When i have deck view selected it displays a limited number of rows, not sure what the limit is, then if I click on details, I noticed it displays all columns regardless of what's set on view. (Possible all the show columns) 

Also the smart chip doesn't revert back to deck view once detail of a row selected. 

An enhancement can be made to filter out only apps and the available views. So after typing the  '@' symbol, a menu saying Appsheet appears with an expand arrow with indexed app names, then a secondary arrow showing available views for that app, I'm sure after saving an app, an index of Deck/Detail views can be stored as a list somewhere. 

Significant improvement from the standpoint of workspace functionality. I'm eager to understand how this feature is being utilised from the developers' viewpoint. I'd greatly appreciate hearing about the various use cases from all the community members present here.

@Rifad Again, a cool feature but agree with you, can't see a use case in my world nor my clients of appsheet. 

We need docs to have easier chart integration from app and better reporting techniques with headers and footers as well types of pagination for many records. 

I see the team is capable of cool things with integration, so please help developers more with docs improvements for appsheet pdf. 

 


@Denzil_Snyman wrote:

in my world nor my clients of appsheet. 


You're correct; it would indeed be more advantageous if the approach was reversed. Being able to preview documents, websites, and PDFs within the AppSheet Desktop UI app itself, rather than from the document, would be more practical.

While the existing features are impressive, for real-world business applications, it seems essential for AppSheet to prioritise functionalities beyond those tailored for marketing.

It's a significant concern that many users, including enterprise-level ones, invest substantial amounts in development, only to discover later that the app lacks basic features like 'copy to clipboard,' leading them down an unexpected and complex path.

 


@Denzil_Snyman wrote:

I see the team is capable of cool things with integration


No platform is perfect, and they all evolve over time. However, the introduction of such 'cool' features often leads us to question the actual priorities of the AppSheet team. It seems their focus might be significantly different from what business users expect or need.


@cschalk_ws wrote:

Availability
Available to Google Workspace customers with AppSheet licenses and AppSheet licenses.


This seems to make no sense.

@cschalk_ws Today I wanted to use this feature. Usecase: I'm writing a report in Google Docs and wanted to insert all the items that are related to this report. So I wanted to insert a smart chip from a filtered deck view. But I get this Error message:

Fabian_Weller_0-1714035572145.png

"Something went wrong when executing the add-on."

Detail Views are working correctly. But not Deck Views.

I've sent also a support ticket.

Deck views should work, you may have hit an intermediate error that requires re-opening the smart chip.

@cschalk_ws Instead of showing IDs, could the smart chip show the label of the related items?

Here is the App:

Fabian_Weller_0-1717487498253.png

Here is how the smart chip looks like:

Fabian_Weller_2-1717487534574.png

 

Good idea, we currently just show the reference keys as the data, I agree it would make sense for references to show the labels for each key instead. 

I've added this as a ticket to my queue.

As mentioned in today's release notes, we've expanded the functionality in the AppSheet for Google Docs Add-On to allow for @ commands allowing to capture user input (form view) or show app details (deck view)! See the documentation: Use AppSheet smart chips in Google Docs for more details.

Here is a quick inline demo:

image.gif

Not sure how many users use this in real business scenarios. 


@Rifad wrote:

You're correct; it would indeed be more advantageous if the approach was reversed. Being able to preview documents, websites, and PDFs within the AppSheet Desktop UI app itself, rather than from the document, would be more practical.


I suggest this is more practical approach. User can tag or use google doc inside appsheet rather than appsheet inside google doc. @nico 

Example: Check out ClickUp's slash commands for integrating Google Drive into ClickUp. It's unfortunate that third-party apps can accomplish this, yet AppSheet, a Google subsidiary, doesn't prioritize such useful features.

https://help.clickup.com/hc/en-us/articles/6308960837911-Use-Slash-Commands

https://help.clickup.com/hc/en-us/articles/14841781940759-Google-Drive-integration#:~:text=the%20att...

Screen Recording 2024-06-05 at 10.47.36.gif

 

I never come up with any practical use cases where smart chips with Google Docs for AppSheet is going to be found useful. So we never used before and never recommended to use to our students (clients).

Basic notion for AppSheet (at that time when it was born before Google Time), AppSheet aimed at centralizing all the related work flow into single place (AppSheet app) to improve the productivities and complex workflow.

Dont let the user to use the other service such as Excel, Google Sheet, Google doc, but just sit on AppSheet apps to run the complex internal/external business workflow.

I spent days and hours, but the smart-chips (with AppSheet app) is not going to give us much of improvement in terms of any business workflow. So I just simply buried this function and untouch.

Im just curious how other find this function is useful and what the practical use cases to employ this functionalities.

 

 


@Koichi_Tsuji wrote:

Basic notion for AppSheet (at that time when it was born before Google Time), AppSheet aimed at centralizing all the related work flow into single place (AppSheet app) to improve the productivities and complex workflow.


You should consider giving ClickUp a try for this use case. They've done an excellent job with customizations and their UI. While not identical to AppSheet, ClickUp offers many improvements, particularly in project management and collaboration.

AppSheet seems limited to basic and niche use cases nowadays, with an outdated UI reminiscent of the 2000s. ClickUp's UI is also highly commendable for the tasks you mentioned. I'd recommend AppSheet primarily for simple data entry, database management, and PDF generation. However, when it comes to database management and automation, AppSheet excels, though it lacks the capabilities for centralized collaboration found in ClickUp. @Koichi_Tsuji 

Screenshot 2024-06-06 at 11.24.33.png

 


@Rifad wrote:

Screen Recording 2024-06-05 at 10.47.36.gif


As shown, while Google is progressing 10x slowly with incomplete features and some less appealing UI designs, competitors have already done them with better innovation for business applications. This sluggishness from AppSheet (GOOGLE) spells doom for AppSheet.

 

 

It is obvious that Google accellrate the integration with AppSheet and other Google Workspace services. It is OK for anyone.

However, the problem is their plan is missing how such a integration is going to bring the benefit to the end users. The recent new features (for AppSheet) is missing this critical point, so the new features such as Smart-Chips, Gemini-AI helping creating Apps, creating table from Forms etc etc, are only found useful by a piece of the users.  

Obvisously the current AppSheet team are only listening to the voice (from their management internally) rather than listening to the voice from the end users. 

Pushing the serious of the none-useful (all of them I never used) features and the posts for feature requests are all ignored is telling all the facts.

Why are we so frastrated ? Just two reasons behind.

(1) Google teams are only keen on internal stuffs, rather than fulfilling end-user requirement. (as always)
      The goal for their team is to fill the internal requirements, needed for promotion etc. rather than satisfying the needs from the end users.

(2) Google never used their own platform (AppSheet) for their own daily business, while we use AppSheet daily. So they never notice the disruptions and outage before the end users notices those.

--

To solve all the issue, the single solution is global Google team, regardless of the countries and places, use AppSheet for thier daily works internally.

Why is the platformer who are not using their own platform daily could recommend such platform to the others ? 

I do have contact with local Google team, but I never see anyone who use AppSheet for their own jobs, so they are not sure how AppSheet works and how the AppSheet is in problem, as they never care because they never use for their daily jobs, while the end users use AppSheet for their critical business requirement to push their daily works ahead.

If Google start to use AppSheet internally and globally, then the story we see now would definitely changes.

To make the story simpler, Google is selling the fruits (apples or oranges) which they never tasted on their own.... They say "this is tasty you shoud try!", but they never taste it before, so those recommended fruits is not sweat, but sour.

 

If we could see AppSheet event where Google team would share their own and internal use cases for Appsheet, how they use AppSheet internally in Google to improve their productivies, then such event is going to be a milestone.

Welcoming to share the their own use cases where their newly added new features are welcomed and used internally and how they do utilize their own tools.

Their own use cases definitely works as a benchmarks for the end-users right here.

 


@cschalk_ws wrote:

Why is this valuable?

Consider a travel plan, trip report or budget request as an example. With AppSheet smart chips:

  • An AppSheet creator could insert a smart chip of all travel requests for a department in a Google Doc, thus enabling a streamlined approval flow and automation without requiring the approver to navigate through the approval app,

I agree with all these COOL features. However, I'm curious about their practical use in real-life business scenarios. How frequently are they actually utilized by any user in any organisation ? Please improve real-life business use case enhancements and usabilities. 

This is a cool feature. But as said, I will find it difficult to make use of it for any process. 

Using the app just seems more simple and fast.

My suggestions : 

A- Improve UI

baba_sawane_0-1717569260583.pngI have a lot of actions in each views, which make sense on the app, but here not. 1 : replace actions name with actions Icon. 2 :  let us select which actions when configuring the smartchip to show OR add a Context("ViewType")= "Smartchip" in appsheet. 3 : make that window wider.

___

B - Enable this feature in Sheets

___

C - Enable more views

As said before this feature should be great most likely in reporting. I don't think being able to edit from a doc would be that useful. But seeing summarized data in a well built UI would certainly be. 

Instead, the edit feature of smartchip would be useful in the context of a ChatApp

 

 

 

@cschalk_ws , Thank you so much for this.

It is absolutely help in our regular task .

Regards

Saddam24k


@nico wrote:

Deck views should work, you may have hit an intermediate error that requires re-opening the smart chip.


Hi @nico I was in contact with the Support team, but di not get an answer since 1 week. That's why I copy my text, because I see that you are involved.
It seems that filtered deck views based on a slice are not working.
Re-opening the smart chip does not help.

Hi AppSheet Team,

Thank you very much for investigating.  The Google Doc that I’ve shared with <PII removed by staff> and <PII removed by staff>  is now working partially. But it takes quite long (about 17 sec) to open the Smart Chip when you hover over it. This is not handy. It seems as if the smart chip syncs the whole app, instead of just the one view that’s linked with the smart chip.

If you think that a whole sync is necessary, then the Google Doc should cache the sync. Because I’ve disabled “Sync on start”. So after the smart chip was opened once and has synced the app, the second time you open the doc and hover over the smart chip, it should not need to sync the app again. Just like it already works when you hover over it a second time while the doc is still open (not closing the doc and open it again).

Or maybe you can do it like that: While creating the smart chip it could sync the app and cache it in the doc.

I say it’s working partially, because sometimes the second smart chip in the shared google doc gives this error. This is the same error that I had from the beginning.

Also the third smart chip of the shared doc is still not working at all. It always gives this error. It never worked.

Fabian_Weller_0-1717584738838.png

I’ve now added a fourth smart chip that gives the error: Url too long. Maximum of 65519 characters. In fact the link has 65538 characters. But I need this link because it’s a filtered view.

Fabian_Weller_1-1717584738841.png

 

Deck views with slice currently require the label column(s) and display (at minimum) of the underlying table to be included, otherwise they don't display well. Agree we should match the web-app for fallback on an appropriate label but as a workaround you can use slices that include both of these columns.

Yes, indeed, it performs a full sync when loading the app -- it could have related table it needs to load for expressions. There are definitely cases we could optimize a lot here.

The `Something went wrong when executing the add-on` is likely due to the app not being runnable (i.e. containing errors). It should have a more user-friendly error which I'm in the processing of adding. Thanks for raising.

And yes, we have a URL limit of 65519 characters, it's quite a high limit already. Two ways to get a shorter url: you use Desktop mode which is generate much shorter urls (you can even just toggle it on temporarily to get the shorter url and switch back). Alternatively if you can move some of the filtering into the slice, that should save a bunch of expressions that are being passed in the URL.

 


@nico wrote:

Deck views with slice currently require the label column(s) and display (at minimum) of the underlying table to be included, otherwise they don't display well. Agree we should match the web-app for fallback on an appropriate label but as a workaround you can use slices that include both of these columns.


Not sure what you mean with this.
BTW I now changed the link so that it does not base on a slice. Stil I get the same error.


@nico wrote:

The `Something went wrong when executing the add-on` is likely due to the app not being runnable (i.e. containing errors).


My App is runnable. So I'm curious about the real reason.


@nico wrote:

you use Desktop mode which is generate much shorter urls (you can even just toggle it on temporarily to get the shorter url and switch back).


This one is working, thank you. Even though I cannot use the desktop mode because some functions I built are not working.
The "Url too long" error is gone, but now I have here, two the "Something went wrong when executing the add-on" error.