Archive: Nintex for Office 365 Knowledge Articles

TopicUnable to view the item under the Repeating Section that connected to a SharePoint Column for an existing item after migrating the Form from Classic or (Old) Responsive Form to New Responsive Form in Nintex Form for Office 365. Instructions Using the Nintex Form Legacy App, revert back to the original Classic or (Old) Responsive Form via Nintex Form for Office 365 Designer. Publish the Form when it in the Classic or (Old) Responsive Form mode. Migrate again to the New Responsive Form. Publish the Form again. Additional InformationThere is a difference in the Repeating Section ID between Classic / Old Responsinve Form and New Responsive Form. Hence, the New Responsive Form is unable to resolve the exising value. By following the instruction as suggested will resolve the issue. 

TopicThe following steps will allow you get a access token for use with the Nintex Forms SPFx API’s when MFA is required.Instructions Obtain the Microsoft.Identity.Client.dll from the NGet package, by extracting it from the downloaded package lib\<net6.0 or net472>\Microsoft.Identity.Client.dll. In the Entra ID app, under the Authentication, add a new Redirect URIs : Platforms: Mobile and desktop applications  Custom redirect URIs: http://localhost In the same directory of the dll, execute this powershell script:  Add-Type  -Path ".\Microsoft.Identity.Client.dll"  $ClientId = "<Client ID>" $TenantId = "<Tenant ID>" $RedirectUri = "http://localhost" [string[]] $Scopes = 'https://<tenant>.sharepoint.com/.default'  $App = [Microsoft.Identity.Client.PublicClientApplicationBuilder]::Create($ClientId).      WithAuthority("https://login.microsoftonline.com/$TenantId/v2.0").      WithRedirectUri($RedirectUri).      Build() $Result = $App.AcquireTokenInteractive($Scopes)

This document addresses design considerations and best practices for creating high-performing Nintex Forms for Office 365. Design Considerations: While there are hard limits on certain elements within SharePoint, several factors can impact the performance of your Nintex form. Here's a breakdown of these factors:  Number and Size of Rules: Complex and numerous rules can slow down your form.  Number of Controls: Adding more controls may increase form loading time.  Custom CSS Size: Extensive custom CSS code can affect performance.  Number of Plugins: Using numerous plugins can add complexity and potentially slow things down.  Number of Lookup Controls: Minimize the use of lookup controls, as they involve data retrieval.  Number of SharePoint Columns: A large number of columns displayed in the form can affect loading times.  Number of Variables using Lookup Functions: Similar to lookup controls, these variables require data retrieval and can slow down performance.  Indicators

Feature:You can upgrade Classic and Old responsive forms to New Responsive forms. When a Classic or Responsive form is ready to be upgraded, a message is displayed in the forms designer when you open the form. After a form is upgraded, a new draft of a New responsive form with the same content type is created.The following video demonstrates upgrading a classic form to a new responsive form.  

TopicA workflow instance immediately fails when it is manually started. The workflow stays in a Started state and the information bubble on the workflow instance details page states:Retrying last request. Next attempt scheduled in less than one minute. Details of last request: HTTP NotFound to [SiteUrl]/_api/web/lists(guid'[ListId]')/Items([ItemId]) Instance Id: [InstanceId] Instructions Navigate to Site Contents > Site Settings > Manage Site Features. Locate the feature titled Workflow can use app permissions. Select Activate. Additional InformationThis article assumes that the user starting the workflow has the appropriate permissions on the site, list, and item. To validate the user's permissions on a list item, right-click on the item, select 'Share', select the icon on the bottom left corner of the 'Share' dialogue window, and review the permission level of the user in question. The Workflow can use app permissions feature, which is a SharePoint Online feature that is not sp

TopicThe following error occurs when attempting to open Nintex Workflow or Forms for Office 365:AADSTS50011: The redirect URI [Tenancy URL] specified in the request does not match the redirect URIs configured for the application '00000003-0000-0ff1-ce00-000000000000Make sure the redirect URI sent in the request matches the one added to your application in the Azure portal. Navigate to https://aka.ms/redirectUriMismatchError to learn more about how to fix this. InstructionsRun the following in the SharePoint Online Management Shell:Install-Module -Name AzureAD -MinimumVersion 2.0.0.71Connect-AzureAD$sharePointOnlineServicePrincipal = Get-AzureADServicePrincipal -Filter "appId eq '00000003-0000-0ff1-ce00-000000000000'"$sharePointOnlineServicePrincipal.ReplyUrls.Add("https://*.sharepoint.com/_forms/*");Set-AzureADServicePrincipal -ObjectId $sharePointOnlineServicePrincipal.ObjectId -ReplyUrls $sharePointOnlineServicePrincipal.ReplyUrls Additional InformationThis issue is due to changes ma

Hi,A few recent posts have asked about having multiple filtering for lookup form controls. I have been with Nintex for over 10 years, and this has been a request from day one. The reason that it was never implemented is because this functionality can be achieved with the current technology. The key to achieving more than two cascading dropdowns is the setup of the lookup lists. There is no limit on the number of cascades. In this example, I will have 3 cascades based on vehicle selection.Users will first choose the Make of the vehicle.The second cascade will then display the relevant Models based on the Make.The third cascade will then have the trim levels based on the Model chosen.To start off with, create 4 lists. 3 lists will be for your lookups, and one list will be where your form is created and data collected.Lists setup.List A has the Makes. It contains one Single lines of text column. List B has the Models in a SIngle lines of text column and a lookup to List A to display the T

TopicWhen a user opens a Nintex Task Form, the page in the browser states "This [site-GUID].sharepoint.com page can't be found"  Instructions This is a known issue.SharePoint is not correctly XML encoding the FormUrl values in each content type definition when the list's content types are being updated (for example: new content types being added, re-ordered). Additional InformationThis is occurring on the SharePoint platform, Nintex has worked with MS on this but is unable to resolve this issue.

ProblemClassic, Responsive, and New Responsive forms may not open or save when they're published on a list within a site that contains an ampersand (&) in the site URL. For example: https://tenant.sharepoint.com/sites/research&development SolutionThis is a known issue. The behavior of each Nintex form type varies between the SharePoint Online Classic and Modern experiences. Each is documented below: Classic Form in Modern Experience: Opens but will not save; an 'Invalid URL value. . .' error will occurClassic Form in Classic Experience: Opens and saves as expected Responsive Form in Modern Experience: Opens but will not save; an 'Invalid URL value. . .' error will occurResponsive Form in Classic Experience: Opens and saves as expected New Responsive Form in Modern Experience: Form will not open, redirected to a page stating 'Page not found'New Responsive Form in Classic Experience: Form will not open, redirected to a page stating 'Page not found'

ProblemIn the List Lookup control, it's possible to type text into the control to filter the results. When a result is selected, the search term remains in the control. This only occurs on List Lookup controls with the 'Allow multiple values' option enabled on New Responsive Forms in Office 365. SolutionThe search term is automatically deleted when a user clicks, or tabs, outside of the control. This is a known behavior with no work around to prevent it. However, this behavior carries no functional consequences.

ProblemYou have a business requirement to display documents in the page viewer control on a Nintex O365 Form to display runtime 'dynamic' values, meaning reading live inputs from the form as the user is changing the control's values.The following steps detail how to display the document either by using a hard-coded URL from the document library or by using a dynamic URL. SolutionThe best way to know if a control supports this type of dynamic value reference is to put focus on the property and look at the Insert Reference options. If you have the option to insert Inline Functions this means that the property will only read the dynamic value when the form is first loading. When you see Inline Functions you will NOT see Named Controls.Another control like the Calculated Control that does support dynamic references will show Runtime Functions and Named Controls, and will NOT show Inline Functions. I have provided screenshots below showing this.Page Viewer Control Settings:The Source URL w

IssueWhen using the 'Web Request' action in Nintex Workflow for Office 365, the following error may occur:Response: 403 FORBIDDEN ["X-SharePointHealthScore=4","SPRequestGuid=e5a6fe9e-2083-1000-2cd5-f703fa2b38b0","request-id=e5a6fe9e-2083-1000-2cd5-f703fa2b38b0","MS-CV=nv6m5YMgABAs1fcD+is4sA.0","Strict-Transport-Security=max-age=31536000","SPRequestDuration=54","SPIisLatency=1","X-Forms_Based_Auth_Required=https:\/\/site url\/_forms\/default.aspx?ReturnUrl=\/_layouts\/15\/error.aspx&Source=%2fsites%2f_vti_bin%2flists.asmx","X-Forms_Based_Auth_Return_Url=https:\/\/site url/_layouts\/15\/error.aspx","X-MSDAVEXT_Error=917656; Access+denied.+Before+opening+files+in+this+location%2c+you+must+first+browse+to+the+web+site+and+select+the+option+to+login+automatically.","X-IDCRL_AUTH_PARAMS_V1=IDCRL Type=\"BPOSIDCRL\", EndPoint=\"\/sites\\/_vti_bin\/idcrl.svc\/\", RootDomain=\"sharepoint.com/<http://sharepoint.com/>", Policy=\"MBI\"","MicrosoftSharePointTeamServices=16.0.0.19214","X-Co

ProblemThe issue is due to the hidden library for the Nintex Forms. Every saved and published Nintex form is saved in a document library at the same site level. The Classic (including the Old Responsive) uses the NinteFormXml library while the New Responsive Forms use the NintexForms library. Nintex Forms does not use the Title column in the document library (this column is inherited from the root Document content type and by default, it is not a required column). However, when this column is made a required field by either enabling the management of content types on the library or by changing the column properties at the root site content type level, you will not be able to save a major version of a file in the library unless you specify a value for the Title column. This scenario would occur when the user tries to publish a form because publish would try to create a major version and this would leave the file checked out until someone manually adds a value to the now required Title f

ProblemWhen MCAS is setup in Office 365 environment, users are unable to open both Workflow and Form because now the URL has changed with additional mcas.ms SolutionNintex currently does not provide any accreditation or official support for Microsoft Cloud App Security (MCAS). If MCAS is enabled then kindly disable MCAS as Nintex is not compatible with MCAS. If you would like to see this feature in Nintex please vote on the following feature request: https://ideas.nintex.com/ideas/IDEA-I-1381

TopicThe For Each action is used to process each index in a collection or dictionary variable. For more information please see the Nintex for Office 365 help files.https://help.nintex.com/en-US/Office365/Designer/Actions/ForEach.htm Video

IssueMicrosoft has announced that they will be deprecating Basic authentication for Outlook, EWS, RPS, POP, IMAP, and EAS protocols in Exchange Online on October 1, 2022. Additional InformationThe only actions impacted by this deprecation are Exchange Online actions. The impacted actions have been updated as of July 4th, 2022 to accommodate this change. Any preexisting Exchange Online actions in workflows must be deleted and recreated, as the new version of the action will offer an 'Authorizing User' field to replace the previous 'Username' and 'Password' fields. Additional information for this change is documented in the Help Documentation and Release notes for Nintex Workflow for Office 365. Related LinksMicrosoft - Deprecation of Basic authentication in Exchange Onlinehttps://docs.microsoft.com/en-us/exchange/clients-and-mobile-in-exchange-online/deprecation-of-basic-authentication-exchange-online Nintex Workflow for Office 365 Exchange Online workflow actionshttps://help.nintex.com

TopicWorkflow actions fail with "An unexpected error occurred on the connection." or "The SaaS provider cannot renew the access token , please re-authenticate the connection to renew the access token". InstructionsRe-authenticate the connection to renew the access token. To do so: Navigating to Site Contents Select 'Nintex Workflow for Office 365' Connections Click on the ellipses next to your connection Select Edit Select 'Update credential details'Once complete, the connection should begin working again without any additional modification to the impacted workflows.Additional InformationIt's expected for a connection to require re-authentication after an extended period of time (i.e. years)Related LinksConnections in Nintex for Office 365https://help.nintex.com/en-US/office365/Workflows/Connections.htm 

TopicHow Is Action Count Calculated in Nintex Workflow for Office 365? Instructions The following actions DO NOT count against the Action Count: • Log to History • Set Workflow Status • Pause for Duration • Beginning Beacon (for use with Hawkeye) • Beacon (for use with Hawkeye) • Ending Beacon (for use with Hawkeye) Any other action should count against the Action Count.Additional Information  Related Links  

QUESTIONIs it possible to revert to a previous design version of a Nintex workflow or form on the Office 365 platform?ANSWERThis is not a feature of Nintex Workflow or Nintex Forms for Office 365, due to the architecture of SharePoint Online. Currently, the only way to revert to a previous version of either a workflow or form design, is to import a locally archived version of the workflow/form. Join the conversation on Version Control in the Nintex Product Feedback Site.ADDITIONAL INFORMATIONRELATED LINKS

TopicHow to create a SharePoint Group in Office 365 environment, and then use that group as a "Participant" in a Task action.   InstructionsGo to Site Setting > People and Group. Add New Group. After the group is created, click Add New User to add member of the Group. 

TopicHow to update the list column with a data type Person or Group (allow multiple value) with an empty value using Nintex Workflow for Office 365.  InstructionsOpen a Nintex Worklfow for Office 365 designer.  Create a "Collection" variable Drag and drop the "Set Workflow Variable" action. Configure this action and set it to update the Collection variable (created in step 1) with value as below Equals : List Lookup Source : Current Item Field : <Column List of Person or Group>. Note: Choose the list column of Person or Group (allow multiple value) that need to be updated.  Drag and drop "Clear Collection" action. Configured the action to clear the Collection variable (created in step 1). Drag and drop "Update List Item" action to update the desired Person or Group (allow multiple value) column list by setting the value with the collection variable (created in step 1).  Publish the workflow.  

TOPICWhen populating a SharePoint list or library Lookup column configured to "Allow multiple values" it is not as simple as just passing semicolon delimited values using the 'Office 365 Create List Item or Document Set' action.INSTRUCTIONSThe Lookup column needs to be populated by inputting the item ID of the item on the list that is being looked up and not its value. Add the action 'Office 365 Create List Item or Document Set' onto a pearl in Nintex workflow Designer Double-click the action to configure it. Specify all mandatory fields as per the help file instruction. See Related Links below. From the 'Fields' section, choose 'Builder' and then 'Add Field'. Configure the 'Field' field with the name of the lookup column that needs populating. Choose 'Lookup' from the 'Type' drop-down menu. In the 'Value' field specify the values with the ID's from the list that is being looked up separated by semicolons. For example: 1;3;6;14ADDITIONAL INFORMATIONObtaining the Item ID's from the list

TopicSorting items in a List Lookup control on Nintex Forms. InstructionsCreate a List View on the source list that is configured to display and order the items as desired. In the Nintex Forms designer, navigate to the configuration for the List Lookup control > General > Source View. Type the name of the desired list view in this field.

TopicYou may experience current workflows are being suspended and no longer running to completion. This is due to numerous deleted association workflows that are ahead of the new running instance.  InstructionsThis is a known issue with 2 possibility of the root cause:1. There are other workflow on the list (if any) to make sure that all the workflow has a Start Option from Workflow Setting (at lease one of the option checked). If all the workflows has the start option, then it related with Microsoft issue that lead us to possibility no 2. 2. Most likely the issue down to a problem with the workflow publishing location associated to the specific site library. Workflow definitions are normally stored in a hidden folder called "wfsvc". This issue creates another folder called "wfsvc1" and puts the workflow there - Microsoft should be able to move the workflows from the wfsvc1 hidden folder to the wfscv hidden folder then remove the wfsvs1 folder. In some cases republishing the workflow m

TopicConfiguring a control on a Nintex Responsive form as Appearance > Visible > "No" puts a "Hidden" message across the control in the Nintex Forms designer and causes the control to not populate it's default value or calculated data. InstructionsThe correct way to achieve the functionality of hiding a control that dynamically populates is to either use a hide rule on the control. Additional InformationThis functionality secures the metadata in the control from being changed in any way.Due to this functionality if you try to hide a control that populates dynamically like a Calculated value control or a single line of text control with a reference the data will not calculate.