Other Related Post

SharePoint Hosting – Resolving The “Out Of Date Nintex Forms” Error In SharePoint Online

Now, I will tell you about how to Resolving The “Out Of Date Nintex Forms” Error In SharePoint Online. While working with Nintex Form for Office 365, you may get this error. Thus, let’s learn all the possible solutions for this error. I have customized my SharePoint Online custom list add Form, using Nintex Forms for Office 365. It worked perfectly. Subsequently, I thought of adding some validations, using JavaScript code. Hence, I followed the steps given below.

SharePoint-2013-Hosting1

– Click on Form Setting on Nintex Form designer screen.

– Under Custom JavaScript option, I simply wrote alert (‘Hello’).

– Subsequently, I published the form.

– Now, when I try to add a new item in my custom list, it opens Nintex Form and I get the error given below.

Once I clicked on OK, the list form closed and default list view was displayed.

Hence, I thought that maybe my Nintex Form for Office 365 app was outdated. I searched how to update Nintex Forms for Office 365 app. I found so many links but I found that my Nintex Form is up to date.

Thus, it gave me trouble. I kept on searching. Finally, I found the solution. When I found the solution, I was really disappointed with Nintex Forms error message, as it is misleading.

The problem was with my JavaScript code and not with the app.

What did I do wrong? I wrote the wrong syntax.

Instead, write the code given below.

The only mistake was I missed the semicolon (;) and I got this error message. I corrected the code and everything was fine and I got an alert message with “Hello”.

Thus, I thought of sharing this, because the error message is somehow misleading in finding the solution.

Thus, when you get the error like this, then do the checks given below.

If you have injected any kind of JavaScript code to Nintex Forms, then please make sure that the code has proper syntax.
If you don’t have any JavaScript code, go for updating Nintex Forms for Office 365 app.
It saved my time to a phenomenal extent. I hope, this will save time for others also.
If you have any query regarding this or you need more information, please feel free to ask in the comment section.

SharePoint Hosting Recommendation

HostForLIFE.eu’s SharePoint 2016 Hosting solution offers a comprehensive feature set that is easy-to-use for new users, yet powerful enough for the most demanding web developer expert. Hosted SharePoint Foundation 2016 is the premiere web-based collaboration and productivity enhancement tool on the market today. With SharePoint 2016 Foundation, you can quickly access and manage documents and information anytime, anywhere though a Web browser in a secure and user friendly way. SharePoint hosting services start at only at €9.99/mo, allowing you to take advantage of the robust feature set for a small business price. HostForLIFE.eu offers a variety of hosted SharePoint Foundation 2016 plans as well as dedicated SharePoint 2016 Foundation options.

hostforlife banner

Sharepoint 2013 Hosting – HostForLIFE.eu :: Sharepoint 2013 Hosting – HostForLIFE.eu ::

In this blog, I am going to perform two actions –

  1. Identify if a page is a modern page or not.
  2. Migrate or copy that modern page (including its content) to another site collection or site (destination location)

I am going to accomplish these tasks by using CSOM (Client Object Model). After identifying the modern page, I will copy the modern page into another site collection (destination location) and then, will migrate all the page contents of this modern page (including web parts and other properties of source modern page) to a destination web using CSOM.

We are using a console application to achieve the above functionality using CSOM. In the below-mentioned code logic, we will get all pages from ‘Site Pages’ page library which is present in the source web and looping each page to check if that is a modern page or not.

If the page is found to be a modern page, then we are migrating that page to the destination web ‘Site Pages’ library.

Please have a look at the below code. The code is self-explanatory because of the comments.
Destination Page Library Before Migration,
Destination Page Library after Migration

After executing the above code behind, you can find the newly created modern page in the destination web ‘Site Pages’ library with the same page contents and “web parts” as they were in the source page.