Archive: Nintex for Office 365 Knowledge Articles

IssueWhen connecting to a database or running an Execute SQL action, the following error occurs:HTTP InternalServerError to https://<domain>.sharepoint.com/<GUIDs>Correlation Id: <GUID>Instance Id: <GUID>Invalid text value.A text field contains invalid data. Please check the value and try again. ResolutionEnsure the Connection String is properly formatted, contains no typographical errors, and is not pointing to a server with a private IP address. Error CodeHTTP InternalServerError to https://YOURDOMAIN.sharepoint.com/ Correlation Id: Instance Id: Invalid text value. A text field contains invalid data. Please check the value and try again. Related LinksConnection String TesterPrivate IPv4 address spaces Wikipedia article 

ISSUEWhen opening Nintex Forms, the following error occurs:Index was outside the bounds of the arrayERROR CODERESOLUTIONReview all site column names and remove any special characters, for example: / : * ? " # % < > |, two consecutive periods (..), or special characters such as a tab.ADDITIONAL INFORMATIONRELATED LINKS

ISSUEWhen selecting a user account during run time, the People Picker control shows a scroll bar.ERROR CODERESOLUTIONRemove the CSS class from the Formatting section of the Panel Control where the People Picker control is located.ADDITIONAL INFORMATIONRELATED LINKS

Issue When update a value to an a list column, you will get get the following error "A text field contains invalid data”   Resolution Your list column may be Single Line Text. When changed to Multiple Line Text the workflow will resume and complete as normal.  

ISSUEWhen running a workflow that contains an "Assign a task" action, the workflow might hang on that action and not report any error, even if the user account is valid.ERROR CODERESOLUTIONReview regular expressions for a string field that is empty or has a NULL value and add a "Run If" action so the regular expression runs only if the String value input is not empty. ADDITIONAL INFORMATIONThis issue occurs when the "String" field of a "Regular Expression action" contains a value that is NULL or empty.RELATED LINKS

IssueWhen using the connection manager in Office 365 actions, this error may occur: The destination site was unable to process request. The provided credentials might not have access ResolutionReconfigure the connection manager and make sure that the credential used has enough permission to execute the functionality as intended. Related LinksConfigure a connection 

IssueWhen updating a personal connection in Nintex Workflow for O365 the new password is entered and saved but the "Last modified" date on the "Available Connections" page is not updated and neither is the password. Resolution1. Make sure that the user who owns the personal connection is logged in.2. Use Internet Explorer to do the update.3. If another browser is being used make sure the user is logged in properly especially when using Multi Factor Authentication. 

ISSUEConnection manager window stuck at loading when creating a new connection.ERROR CODERESOLUTIONAdd the below url to trusted sites in Internet Explorer options. https://*.sharepoint.com https://*.nintex.io https://*.microsoftonline.comADDITIONAL INFORMATIONRELATED LINKS

IssueWhen creating a new template with Document Generation action using Office 365, the following error may be displayed:'Nintex O365 Document Generation: A file with the name word.docx already exists. It was last modified by user01 on dd/mm/yyy 00:00:00' ResolutionCreate a new document library then select this library within the Document Generation action to create or select an existing template. Additional InformationThe root cause of this issue due to the document library being corrupted.  

IssueWhen opening a Nintex Form for a List that has a special character in the title, The site navigation link, at the top left of the Form, displays an encoded list name. For example, the list name is Nintex@List, the site link navigation shows Site > Nintex%40List instead of Site > Nintex@List.    ResolutionThe issue has been fixed on the latest version of Nintex Form for Office 365, that has been released at the end of August 2018. Make sure that the site has the latest version of Nintex Apps. 

IssueWhen creating a Connection in the Nintex Workflow Gallery in Office 365, an error window appears with:“Error creating connection. Bad Request - {"correlationId":"00000x0x-0000-xx00-x00x-00000x0000xx","code":"CM-ERR-00005","message":"Incorrect or incomplete input data. [WebTitle]","_links":null,"_embedded":null}”  Resolution-In Office 365, navigate to the App Launcher (dotted square in the top left corner) > Admin-You are now in the Microsoft 365 Admin Center. Click the > in the top left to expand the menu-Navigate to Admin Centers > SharePoint > Site Collections-Locate the Site Collection in which you are making the Connection to-Select the site and open the Properties for the site-Ensure that the 'Title' field is populated. If this is blank, you must enter a title.  Error Code“Error creating connection. Bad Request - {"correlationId":"80003c4f-0003-df00-b63f-84710c7967bb","code":"CM-ERR-00005","message":"Incorrect or incomplete input data. [WebTitle]","_links":null,"_

IssueWhen attempting to open a form after an item was submitted, the follow error occurs: An embedded page at formso365.nintex.com - An error occurred during an Ajax call. Resolution Find either the current GUID of the form, or the list GUID (ID) Navigate to https://SiteURL/NintexFormXML/ Identify the form xml here that is associated with your list. These items use the naming structure `FormID_ListID` (edited) Click the ellipses by the form associated with the list and select version history. Restore the previous version of the form (Note: you may need to roll back further versions if multiple versions of the XML are corrupt). Navigate back to the list where the issue occurred. Open the forms designer to ensure the issue is resolved. Error CodeAn embedded page at formso365.nintex.com - An error occurred during an Ajax call. Additional InformationThe root cause of this issue is currently unknown.  The reason for the AJAX error is due to the XML located in the NintexFormXML library bein

IssueWhen using fn-formatdate to format the date into a certain format, the runtime function will only work in the VIEW mode and doesn't work for in the NEW or EDIT mode.  ResolutionThis is by design, the fn-formatdate only works in the VIEW mode; in EDIT and NEW mode, the date format will follow the Site's Regional setting. 

IssueWhen a workflow has an Action Set configured to "Run contained actions at elevated app permissions," the workflowfails for all users, regardless of permission level, upon entering the action set.  Without the Action Set configured to "Run contained actions at elevated app permissions," the workflow works without issue. ResolutionNavigate to Site Settings > Manage site features Deactivate "Workflows can use app permissions" Re-activate the same feature 

IssueWhen opening a Nintex Workflow for Office 365, a dialog box with the below error ,messages appears:Oops! Something went wrongAfter closing the dialog box, the user will able to open Nintex Workflow designer without any issue. ResolutionClose the error dialog box. Open Nintex Workflow designer.  Save and Publish workflow.  Additional InformationThe error only happened for a new tenancy. This error will disappear after at least 1 workflow is published.  If this error appears on a page and not a dialog box open SharePoint Online Management Shell, connect to your tenant and run the command:Set-SPOTenant -DisableCustomAppAuthentication $false To install the SharePoint Online Management Shell you can start by downloading and running the SharePoint Online Management Shell or installing the module from the PowerShell Gallery. Once installed, the module is available for use, and you do not need to install it again until you need features introduced in a later version. Thereafter run the cm

IssueWhen using a Managed Metadata term value within a text field, such as an email body, or Log To History action, the term displays as 'Value | TermIdGUID'Example: 'Nintex Engineer | b664989e-0ac2-4d49-9a89-d6f7bf092fe1' ResolutionThis is expected behavior when converting a Managed Metadata term to a string. You can use the Regular Expression action with the following configuration to strip out the GUID:String: {Variable:OriginalManagedMetadataTerm} String operation: Replace Pattern: |(.*) Replacement String: Output: {Variable:UpdatedManagedMetadataTerm} 

IssueWhen Hide formatting rules execute on a form at runtime, controls lose their placement. ResolutionAdd a Panel control and nest the moving controls within the panel Remove the ‘Hide’ rule from the controls Apply the 'Hide' rule to the Panel and NOT the individual nested controls  

IssueWhen a responsive form has a confirmation message and redirects to a specified URL, the form will hang when using the Save button within the ribbon of the form. ResolutionThis is a known defect with the current release of Nintex Forms for Office 365.Using the Save button on the form itself does not cause this behavior. 

IssueWhen trying to export a workflow from the Nintex for Office 365 designer, the export fails with the error: "Workflow is too big, please reduce some of the actions." ResolutionRemove an disabled/un-needed actions Break the workflow into smaller parts and export the new child workflows  Error CodeWorkflow is too big, please reduce some of the actions. Related LinksSharePoint Workflow Thresholds 

IssueWhen setting the value for a Choice control on the form, the value is not being saved or reflected in the connected column on the list.  ResolutionVerify that there is only one Choice control connected to the choice field on the list. If there is more than one connected control, the value from the lowest control on the form (closest to the bottom of the form) will be saved back to the list, and as such reflected back into the higher control on view or edit of the from. 

IssueUnable to access the existing connections with the account was utilized to create the connections.Error CodeOops! Something went wrong. Unauthorized access while getting connection list    ResolutionTo resolve the issue, re-trust the Nintex workflow app following the below steps: 1. Navigate to the site contents2. Switch to classic mode of sharepoint3. Hover over the Nintex workflow app and click on the ellipsis >> then next ellipsis and clcik on permissions4. On the last line, then click on here link to trust the app. Additional Information  Related Links  

IssueThe below error is generated whilst adding a user to the "Administrator Management" page in Office 365 Error: ResolutionEnsure the Administrator management page is accessed via the Nintex workflow app, from within Sharepoint, rather than using a saved URL. 

IssueA workflow is run and suspends with the error System.InvalidCastException:   ResolutionAn invalid cast occurs when a source data type is being transformed into a destination data type but the conversion cannot take place because the data types are not compatible.  An example would be trying to transform a text string into a date/time.Any action that can do a conversion should be checked to make sure that the data going in is compatible with the data that is required to come out of the action. Error CodeEXAMPLE: RequestorId: 72cd8e33-f740-0000-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.InvalidCastException: String at Microsoft.Activities.GetDynamicValueProperty`1.CheckedRead(String propertyName, DynamicItem value) at Microsoft.Activities.GetDynamicValueProperty`1.Execute(CodeActivityContext context) at System.Activities.CodeActivity`1.InternalExecute(ActivityInstance instance, ActivityExecutor

ISSUEWhen clicking the button "Grant Access To Workflow" as per these instruction, the following error occurs: Sorry, something went wrongThe app <GUID> does not exists.ERROR CODERESOLUTIONNavigate to the site URL that is going to be trusted. e.g. https://companyname.sharepoint.com/sites/HR Then navigate to the Workflow App ID from the workflow by following the instruction below: Go to Site Setting > Site app permissions. Find the app display name Workflow (Note : NOT NINTEX WORKLFOW). Get the value of App Identifier of the app display name Workflow. The app ID is between ms.sp.ext| and the @ symbol, for example the App Identifier is i:0i.t|ms.sp.ext|23803489e-0e9e-4fc3-a3b3-e2bd7599c5ad@a6f890769-0c2d-46f7-9480-072519e051ed. The App ID is 23803489e-0e9e-4fc3-a3b3-e2bd7599c5ad. Once we have the URL (step 1) and the App ID (step 2) , we can make a link with this format below: {SiteAddress}/_layouts/15/OAuthAuthorize.aspx?client_id={AppID}&scope=AllProfiles.Read&resp

IssueThe below error occurs when attempting to publish a Nintex workflow that contains a conditional start event.Error message:Error publishing workflow. Conditions could not be published and the workflow will not be able to start conditionally. Please try publishing again. ResolutionPublishing a Nintex conditional workflow will use 1 subscription per published workflow. SharePoint only allows 100 subscriptions on a custom list and it is possible that the list has reached the maximum number. Other third party products can also use subscriptions for example Microsoft Flow.Options:1. Recreate the SharePoint list.2. Contact Microsoft Support to assist with removing subscriptions from the SharePoint list. Error CodeError publishing workflow. Conditions could not be published and the workflow will not be able to start conditionally. Please try publishing again.