Hi Cassy Freeman‌, 

Thanks for the feedback. I will chat to the development team.

Cheers,

Euan

Any update on this topic?

Hi, 

I'm facing the same exact problème. Any updates about this?

Regards!

Hi, 

I found a solution to this problem :

NWF$(document).ready(function () {

    NWF.FormFiller.Events.RegisterAfterReady(function () {

        var button = NWF$('.saveButton');

        button.removeAttr("onclick");

        button.click(function () {

            var listUrl = _spPageContextInfo.listUrl;

            var listName = "Customer Contract";

            var parameter = "itemStatus";

            var value = "new";

            var elementName = NWF$('.saveButton').last().attr('name');

            var aspForm = NWF$("formmid=aspnetForm]");

            var oldPostbackUrl = aspForm.get(0).action;

            var currentSourceValue = GetUrlKeyValue("Source", true, oldPostbackUrl);

            var dsName = NWF$('#' + calcName).val();// the name of your document set

            var newPostbackUrl = oldPostbackUrl.replace(currentSourceValue, listUrl + "/" + dsName);

            if (!PreSaveItem()) return false;

            WebForm_DoPostBackWithOptions(new WebForm_PostBackOptions(elementName, "", true, "", newPostbackUrl, false, true));

        });

    });

});

@bekri Where would that code go? And does it work on both Responsive and Classic Forms?

Hi @smarano, 

This code goes in a custom javascript that you have to reference in your form "form settings".

I didn't try it for responsive but it's Javascript there is no reason it will not work.

Let me know if you need more details

Responsive Forms removed all support for JavaScript, and while you technically still *can* get it working inside of that form type, it is not and will never be supported by Nintex and is also rather advanced in terms of knowing JS. 

For Classic Forms however, you should be absolutely fine to go! 

Any update for this for Responsive Forms? Having the same issue.

Hi Euan, Could you please let us know if you have any update on this for Old responsive forms on Office 365? We have the same issue. I tried to use Form variables to redirect on "Save" button, but there is no reference available to add Form variables. Could you please fix this?

Any update on this? I don’t want users to have to search through a library of hundreds of doc sets to find the one they just created. Not using a Nintex form is the only option if I want to make sure a user is directed inside the newly created doc set upon saving.