more than 100 widgets

384 views
Skip to first unread message

Fahad Sulaiman

unread,
Jul 22, 2022, 12:28:22 AM7/22/22
to Google Apps Script Community
hi,
its known that we have only 100 widgets in card servrvice...is there any workaround to have more than 100 widget...

Paul Armstrong

unread,
Jul 22, 2022, 7:27:30 PM7/22/22
to Google Apps Script Community
A [Next] button on the footer? 

All my workarounds for card service have involved me making compromises on the UI. I have not found any real hacks that get the platform to do what I want outside of how it was designed. Often I do find it does a little more than I expected, so I am more careful with reviewing all relevant documentation and searching for examples to match what I am trying to do. But if I can't, I move on and change the way I have structured the UI. 

Good luck!

Clark Lind

unread,
Jul 23, 2022, 8:39:49 AM7/23/22
to Google Apps Script Community
As Paul mentioned, your best option is to restructure your UI. If you have more than 100 input fields for example, then break the input data into logical groupings with each grouping having its own card. 
If you are displaying information or photos or something, just display the maximum you can including Headings, section headings, etc, and add a "Next" button to call the next card...
Cards and Card Service is very strict, similar to G-Forms, there is only so much you can do within the framework provided.

Fahad Sulaiman

unread,
Jul 24, 2022, 3:03:34 AM7/24/22
to google-apps-sc...@googlegroups.com
but if i created new card, then previous form data will be removed...how to handle that..

--
You received this message because you are subscribed to the Google Groups "Google Apps Script Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-apps-script-c...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-apps-script-community/d301d060-ffc1-44b8-95e3-67fb6dc17581n%40googlegroups.com.

Clark Lind

unread,
Jul 24, 2022, 8:31:04 AM7/24/22
to Google Apps Script Community
You could store the input data using the Properties Service. Then, when all the required data has been input, grab it all out of PropertiesService at the end and process it. I think that is how I would handle it. Depending on the context, you can either store the data with the User (userProperties), with the specific Document (documentProperties), or with the Script itself (scriptProperties).

Clark Lind

unread,
Jul 24, 2022, 8:36:19 AM7/24/22
to Google Apps Script Community
Also, if you have access to and can use Firebase, that would be the preferred method I think.
Reply all
Reply to author
Forward
0 new messages