Skip to main content
Nintex Community Menu Bar

jquery.SPServices CAML query no working on Nintex form

  • June 23, 2017
  • 2 replies
  • 32 views
  • Translate

Forum|alt.badge.img+3

I trying to call a jquery.SPServices CAML query, It work on normal Sharepoint form, but fail on Nintex Form.

 

This is what have i done on the Nintex form,

Add the JavaScript reference library to the Custom JavaScript Includes (under form settings)

https://ajax.googleapis.com/ajax/libs/jquery/1.11.2/jquery.min.js 

https://mySharepointSite/SiteAssets/jquery.SPServices-0.7.2.min.js
https://mySharepointSite/SiteAssets/SupplierRegister_OpenAccount.js

 

 

https://mySharepointSite/SiteAssets/SupplierRegister_OpenAccount.js

204856_pastedImage_4.png

 

 Where executing, on line 12, its always return "parserror".

204862_pastedImage_1.png

 

Please help. Thank you.

 

 

Further drill down. I found this on the response message.

204881_pastedImage_1.png

 

I believe its because the Nintex Form Iframe cause this problem.......

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

2 replies

Forum|alt.badge.img+11
  • Scout
  • 468 replies
  • June 26, 2017

Hi,

I think that the issue is that every O365 app runs in a different web site (if your tenant is https://contoso.sharepoint.com, each app will run in something like https://contoso-<guid>.sharepoint.com)

so, when SPServices try to do a call on /_vti_bin/lists.asmx, it does it in the current context, so the call goes to https://contoso-<guid>.sharepoint.com/_vti_bin/lists.asmx that doesn't exist..honestly, unless you change spservices code to strip the guid part of the base url, I don't think it will work with Nintex or with any other app, sorry...

Giacomo

Translate

  • 4 replies
  • January 23, 2020

It looks like SPService is no longer working for Nintex forms in O365. Does Nintex provide any solution for that?

Translate

Reply


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