Will this ever be released?
Google changed the Sheets API between the time this was written and now. leading to some rewrites that have slowed the component down. I hope to have a new component available for testing in the near future.
This is the more recent thread. I believe I may have accidentally overwritten the test server, however.
it's been nearly 2 years now, Google Sheets Component works fine, will it be added in next update.
Let me know that the test server will not shutdown in future as I may lost all the projects, if it gets shut down
@Shanmuga_Nathan We're not prepared to include it in the next release, but it's in final review with the dev team. Assuming no other significant bugs are found, it should release in the near future.
It sounds like you've been doing some significant work with the component and find it works well. Could you give me some idea of the kinds of projects you've been using the component for? This is incredibly valuable feedback. It's difficult for the team to approve and merge big, complex changes like this because we are small, and it's very difficult to test them completely. This component required quite a bit of redesign because of changes Google made to its API.
Feedback from you and anyone else who is using the component on the test server can speed up our approval process.
As far as your projects, I recommend you keep backups. Export them to your computer using the "Export all Projects" option from the Projects drop-down menu. When we merge the component, you will need to import your projects on the normal server. Also, though I have no immediate plans to take down the test server, it's just a test server with no guarantees. Many things could happen, including things completely out of my control, that could wipe it out.
I just need to say that it's the best alternative to Firebase Database, the speed of this component is equal to the speed of Firebase DB and the notable thing is the API **% completely free** with 300 read and write requests per minute.
Also no coding knowledge is required like Firebase DB as the Google Sheets Component is basically an Excel sheet.
TEST server is too old, and i cannot copy screens, I'm just testing out the component and all blocks on a regular basis and providing feedback. If you upgrade the test server version to latest, then I can provide all my project ideas even with free AIA
I hope the main purpose of MIT APP INVENTOR is no code, then This component will be easy for beginners and zero coders to create a no code private and secured Database at no cost.
Hope the team will bring the component soon in next few future release.
I understand, but if the test server is gonna Wipeout, please send a reminder date to the users, as it might be very useful to take project backups.
(added to FAQ)
Sir, When i build apk file, there is an error. Server error: could not build target. Please try again later!.
The spreadsheet component has been published, so the test server in this thread is no longer relevant. Please move any projects from the test server to either ai2.appinventor.mit.edu or code.appinventor.mit.edu.
4 posts were split to a new topic: Transferred from Google Sheets Test Server to aia server. Save to PDf no longer works
A post was merged into an existing topic: Transferred from Google Sheets Test Server to aia server. Save to PDf no longer works
Started a new topic for this, as not related to Google Sheets Component
sorry I'm a beginner, I tried to post data to google spreadsheets but it failed, am I wrong in creating the credentials or the block, please help me..
Did you create the ,json file mentioned in
and upload it to the Media folder?
Did you create a Google Project?
Did you create a service account email address?
Did you share update permission to your sheet with that service account?
What was the error message?
yes sir, i have done it, i have created developer account, service account, generated key in json format then upload in media, but i failed to enter data into google spreadsheet
Pull in the Spreadsheet event block that catches errors, and have it post the error to a Notifier with an OK button, so you can catch and show the error here.