Skip to main content
Nintex Community Menu Bar
Solved

Web Request Action Error – Office 365 (using Google API)

  • June 3, 2016
  • 7 replies
  • 9 views
  • Translate
P
Forum|alt.badge.img+8

I am attempting to use Google's API through an O365 Web Request to do some geocode translation. I've been able to reproduce a similar implementation using Nintex Workflows for SharePoint 2013 (on-prem) but am having trouble with O365.

 

This is the error my Web Request action is producing:

Screen Shot 2016-06-03 at 12.59.53 PM.png

"Some parameters failed the validation check. - [InputFileContent] : The parameter or the parameter value is null.

 

If you take a look at the below URL, it returns the XML data I'm needing so I'm not sure why doing so within the context of Nintex is giving me so much trouble and am hoping it's something minor I'm missing. Any ideas?

https://maps.googleapis.com/maps/api/geocode/xml?latlng=34.7553595,-86.6945471&key=AIzaSyC2XrDaswnI72kZrzfTpU0IalfUnmqGS…

 

Screen Shot 2016-06-03 at 1.04.24 PM.png

 

Vadim Tabakman​ Brad Orluk​

Best answer by vadim_tabakman

Yep in O365.

I've attached the workflow here.

View original
    Did this topic help you find an answer to your question?

    7 replies

    vadim_tabakman
    Nintex Employee
    Forum|alt.badge.img+11

    Hi Patrick,

    I took that same url and tried it in a workflow and it seemed to work fine.  I got the expected results back.

    Could it be the way you are building up the url?  Maybe there are some spaces in some fields?

    Vadim

    Translate
    P
    Forum|alt.badge.img+8

    Did you try within O365?

    I was able to make this work with on-prem, but not with the Web Request control in O365.

    Get Outlook for Android<https://aka.ms/ghei36>

    Translate
    vadim_tabakman
    Nintex Employee
    Forum|alt.badge.img+11
    • vadim_tabakmanNintex Employee
    • Nintex Employee
    • 309 replies
    • Answer
    • June 6, 2016

    Yep in O365.

    I've attached the workflow here.

    Translate
    1 Attachments
    P
    1 person likes this
    • P
      patrickabel
    P
    Forum|alt.badge.img+8

    Thanks Vadim Tabakman​ – I really appreciate the help! Let me give this workflow a try and see if this gets me past my impediment.

    I was pasting in the URL, but had actually pulled out all of the dynamic components for the API key and coordinates so I don't believe that was causing the problem.

    Translate
    P
    Forum|alt.badge.img+8

    Vadim Tabakman​ Although I thought I had tried each possible configuration, setting up the Web Request control as a GET solved my issue. Thank you sir!

    Translate
    vadim_tabakman
    Nintex Employee
    Forum|alt.badge.img+11

    Oh nice one.  Glad you figured out what it was.

    When I was testing it today, I almost made it a POST, because that's what I thought it would be.

    Vadim

    Translate
    P
    Forum|alt.badge.img+8

    Haha that was my instinct as well with what I've done before with ajax so I think I just overlooked it. I was comparing it to the UDA you and Brad Orluk​ shared a while back and I believe it was setup as a post for the on-prem solution.

    Thanks for helping me resolve this one Vadim Tabakman!

    Translate
    B
    1 person likes this
    • B
      brad_orluk

    Reply


    Sidebar Buttons
    Nintex Community Home Contact Nintex Support Email Nintex Community Check Nintex Status
    Terms & ConditionsCookie Settings

    Cookie policy

    We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

     
    Cookie Settings