Skip to main content
Nintex Community Menu Bar

Hi, 

 

I have created a responsive Nintex Form and now would like to link to this from a page in SharePoint. I tried copying the link from when I clicked on +New for the list but this works once and then stops working.  

Where can I get a link that always works?

KR

Sandy

provided you only have one content type on your list you should be able to get it simply by using the following:

https://yourdomain/sites/yoursite/lists/yourlistname/newform.aspx

the bold  portions being the bits you'll need to substitute with your domain, site and list.

This will work for both O365 and on prem.

If you have multiple content types on a list and different forms for them then you'll need to include the query string ctype parameter.

If you want to redirect when the form is closed you will want to include the source parameter in your query string. However you can also control this in your button settings.


Thank You, I didn’t realise that this would be the link.

Kind Regards

Sandy Huntley Application Support Specialist • Business Solutions and Technology

Tourism and Events Queensland

T 61 7 3535-5514<tel:61735355514> • E sandy.huntley@queensland.com<mailto:sandy.huntley@queensland.com> • W teq.queensland.com

A Level 10, 30 Makerston Street, Brisbane QLD 4000<https://www.google.com/maps/place/30MakerstonSt,BrisbaneCityQLD4000,+Australia/> • GPO Box 328, Brisbane QLD 4001, Australia

I know just the place to plan your next Queensland holiday: queensland.com<http://www.queensland.com/>

Follow us on: Facebook<http://www.facebook.com/visitqueensland> Twitter <http://twitter.com/queensland> YouTube<http://www.youtube.com/queensland>


No problem.

If this answers your question, please mark as an answer so future users can find it.

Thanks


Could you share an example of what the New form URL would be for an O365 list with multiple content types with unique custom nintex forms? I appreciate how to obtain the ctype ID from the default new URL of the list content type, but would appreciate your input on the overall format.


This works for me

https://domain/sites/sitename/Lists/listname/newform.aspx?ctype=0x0100B27D341B5956CE46AC0FB85C448

The ctype value in my url is an indicative value obviously. You can obtain your content type ID by going to the content type settings within List settings.


Thanks for the quick response.

Are you achieving the customised CT link in O365?  reviewing the URLs of the various CT's with individual Nintex forms, they include the app sub domain in the URL. When I attempt the following - the new form for the default list 'item' displays, and not the desired CT newform;


https://domain.sharepoint.com/sites/sitename/subsitename/Lists/listname/newform.aspx?ctype=0x01009357285F3AB7E44FA294F6788D78B2C901008F7060120C10B040BC9AE58B8A312F3B


You're right. It does appear that in O365 with multiple content types you need to invoke the full URL including the app sub domain to be able to give a direct link to the new form.

If you wanted to give a link direct to an existing item you'd want to copy the link from form in Edit mode rather than New mode. The main difference here is a query string parameter called mode (1 = edit mode, 0 = new mode) and there's also an ID parameter in there, which is the ID of the item in the list. Not as clean as on prem but then there are the constraints of the app model to deal with.


Instead of ?ctype= try ?ContentTypeID= . I just ran into a similar issue. When I use ctype it pulls up an old version of the form (be it Nintex or stock SP form) but ContentTypeID seems to work correctly every time.


I realize that this is an older conversation, but when I add the source query string param to point to another page, the "redirect" or return or whatever the URL gods call it doesn't work in newer browsers.



 



What I am doing is linking to a task form (Nintex form) from a link in an email where the source param has been added to point to an aspx page that has some simple JavaScript embedded to close the window.



 



Could it just be that our browsers are now outsmarting us?


Reply