Accessing Google Services - Part 1

Buried within the layers of complexity inside any technical system are the simple settings of multiple parameters and/or settings. You simply need to get the right pieces into the right places. You know - like a jigsaw puzzle.

And, once the puzzle starts to reveal itself, the understanding of what the picture is becomes so much more clear. That's the goal of this particular video when it comes to connecting to the myriad of possible Google services.

FileMaker Pro, in the last few years, had improved by leaps and bounds with regards to working with external systems and services. With everything you need now built in the the native client, you can easily connect to Google's services and make the most of them right within your own FileMaker solution. You may just need a head start on the understanding in order to see the whole picture. Fortunate, that's exactly what this video will do for you. If you need to connect to Google services for any reason then look no further!

AttachmentSize
GoogleOauth2.zip89.72 KB

Comments

Matt,
I am so so happy that your covering this!!! I have been struggling how to do this and now with this video I am not so lost in the sauce!!!! Thanks so much!!! I am so happy you're going to use sheets for the next video, because I have had an online application ran by google forms for over a year and currently the users are copying and pasting the application into the solution from a PDF that is being emailed to them once a new form is submitted. I've told them one day I will dive into Google api's to determine how to somehow allow them to import data from sheets into the solution which will save them so much time and make me a hero... Because otherwise I was going to have to make a general user for my solution to allow applicants to log in and fill out a application on the solution which I have held off from doing due to security concerns.

Matt,
I have a question, I followed along with your video and tried this on my solution but could not get past the Run X Y due to the following error "The File "XYZ" could not be opened. Either the host is not available, or the file is not available on that host. I know my solution is hosted on a server so just to double check, I added my google info into your file you supplied and it is still giving me that error. So what do you think that I may have done to break this solution. My other question is about the authorized redirect urls "www.domain.com/googleauth/", Do I need to make a page on my website that is called this? Or is this solution making that url? I will keep playing around with your solution to triple check my steps while I await your guidance.

Okay, So after watching your video again, I have figured out that it was having Filemaker 16 and 17 on my Mac. So I thought that 17 was going to work but that was the one with the errors. But when I tried in 16 (set as default on Mac). the Run fmpURL Direct still errors out with the same error but at least the Run fmpURL HTML works :)
And when I use your solution on Filemaker 16 they both work so I am unsure if the issue is because it is hosted on a server which according to the shortcut I created my users is "bplist00—SURL_hfmp://dbserve.mydomain.com/TEST%20-%20ONE%20TWO%20THREE%20FOUR%20Five "

So after looking around, I was able to resolve the authorized redirect url mismatch :) the issues was my mistake on the project.

The only issue I am having now is only the Run fmpURL Direct is still giving me the same error but the Run fmpURL HTML and Authorize google account is working as shown in my solution.. Thanks so much again for this vital information!

Hi Matt,

This is really useful stuff. However I've hit a few roadblocks early on.
On the OAuth Consent Screen it's asking for an application homepage and privacy policy page. It's indicating that Drive metadata is a sensitive scope and therefore all of my submitted URI's require verification which could take up to 7 weeks.
I feel I must have taken a wrong turn here in the Google APIs and Services setup steps.
Thanks,
Morgan

Morgan Chance - Digital Fusion

This works perfectly on my Mac, but with FM Go I get an authorization error. Error 403: disallowed_useragent. I have it kind of working by using open URL script step with the googleauth custom function as the URL. It authenticates and opens the script in FileMaker Go. I suspect I need to pull out the token and so on as vars on that hosted page and pass the vars as parameters in the FM Script. I'm having a little trouble on the javascript end getting the vars, but am I basically correct on FM Go?

Jim Marshall