Hi

I think I found something.

The link to the item I got from right clicking on it and copy link. 

Or with the same result get the “Item URL” reference from a Nintex Workflow.
Which ends with. “/DispForm.aspx?ID=1”

If i manually add the content type ID to the end URL the link works to the Nintex form including the “Change content type” control.

But if you dont use Nintex forms but SharePoint regular forms and use the regular link even if there are diffrent content types those links work. So it is only the “Change content type” control that makes the standard link to the item not able to open.

I hope it is possible to follow my ramblings :)

Is this a bug or something Nintex can look at?

Best regards Tommy

Hi @tommy 

this is normal behaviour, by adding in the content types the URL requires 2 query string parameters to work, it should however pick up this fact and links with the right ID should auto populate the contenttypeid query string and this is done via redirect however most browsers now prevent this behaviour which might be why you get this error. 
 

At form level it is fairly easy to detect that an item requires this but on a workflow level, not so much, can you try creating a new workflow to see if the Item URL variable populates correctly in a new workflow? I have a feeling existing workflows will not account for content type changes. 
 

If it does work well then you can create a new workflow, you could go about migrating the old workflow definition into the new one or just accept for this workflow you need to remember to add content type to the query string url. 
 

Hi Jake

Thank you for the reply. The “Item URL” from the workflow variable works fine when I have diffrent content types. And I dont get the redirect error. It is just when I add the “Change content type” control to the Nintex form. Then even created link stops to work (if they dont contain the content type).

So, like you said it looks like the automaticlly population of the content type works as long as I dont add the “Change content type” to the form. So, if I want the “Change content type” control in the form I will need to make my own workflow variable that contains the content type and add it to the item URL.

It didnt make a diffrent when making a new workflow from scrats.

Even if I do this, I know some users will send links to an item which will then not open because they forget the content types. I think many will right click and copy link on the items and that will not include the content types. And I think I will get a lot of support tickets on that.

So, I think I will be looking into either remove the “Change content type” control from the form all together. And made make a workflow that change it if you press a button. But that will take the user out to the list and need to reload the item again. But it should open item links even without the content type included.

Or work with “Hide” rules on panels instead of content types all together. To go around the problem.

Best regards Tommy

Hi @tommy 

I have not seen that behaviour before and I don’t why adding a field to the form will cause it, I would definitely investigate it with our support team to find out what is happening and if it is perhaps a bug. 

Content types are definitely the much better method to handle form types, changing to using rules only makes everything more complex.

Just to note however, in newer forms designers there is no longer a change content type control, perhaps this is why I am not sure. 

Jake

Hi Jake

Thank you :)
Lets see if you come to the same issue as me.

A little sad that the “Change content type” control is removed in new Nintex forms. But the “Page” options works just as fine or better :)

Just a little curious if the “Change content type” is removed and it is a good function. How do you use it? How do you navigate your users to the diffrent content types? With workflow?

Best regards Tommy

Hi @tommy 

in newer forms I typically use a control field that is handled with a workflow to change the content types, a lot of the time however changing content types mid life of the form is rare and just does not make sense to support it. 
 

as you mentioned a lot of the reasons why can actually be handled in the new forms designer, for example one of the main reasons I use them is to present fields with different questions, this however is something the new rule designer can do by renaming fields based on condition. 
 

Jake