Archive: Nintex for Office 365 Knowledge Articles

IssueWhen using a Send an Email actions in Nintex Workflow for Office 365 and configured formatting (font, size, etc) at the email's body with insert references values, the insert references values will not have the the expected format as configured.  ResolutionIn a new Send an Email action. Enter the email body with only text including the text that will be replaced with insert reference in step 4. At this stage DO NOT insert any reference (item properties, workflow context or workflow variable). For example if the requirement is to have the Created By value from the current item, instead of insert the reference as explained here, just write down as normal text Created By.  Highlight all the email body that has been written in step 2 and change the text format (font, size, etc) as desired.  Replaced the normal text Created By on step 2 with the actual insert reference from the current item. Now it looks like {CurrentItem:CreatedBy}. Publish the workflow Related LinksInsert Reference P

IssueIn Nintex forms when using a label and populating that label with an Item property changed ToUpper and it has the ”&” character it will crash the form and error with "Reference-to-undeclared-entity-AMP" on form load.  ResolutionA fix for this defect was released in April. Update to the latest version of Nintex Forms for Office 365 app. 

IssueWhen using the Office 365 workflow actions, the workflow instance suspends with the error: 'Unable obtain security token, authentication failed.' ResolutionVerify that the account being used does not have Multi-Factor Authentication (MFA) enabled, as MFA is not currently supported by Nintex for Office 365 Verify that the action works with an @domain.onmicrosoft.com account vs. an @domain.com account. Success with an @domain.onmicrosft.com account vs a domain account will indicate an issue with ADFS. The Microsoft Remote Connectivity Analyzer can be used to investigate ADFS issues further.  Error CodeUnable obtain security token, authentication failed. Additional InformationSteps for testing with Microsoft Remote Connectivity Analyzer: Microsoft Remote Connectivity Analyzer Select Office 365 tab Under Office 365 General Tests select 'Office 365 Single Sign-On Test' Select 'Next' Fill in domain user credentials and the verification captcha Select 'Perform Test' Review results for A

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 opening an existing Nintex Forms Office 365 for editing in the Nintex Forms designer the form does not load and the designer is stuck on the spinner.The existing form works and can be used for new, edit and view but the form cannot be opened in the designer. ResolutionIt is possible that the form has been edited and saved in the designer but a file has become corrupted.To get back to the previous form follow these steps. 1. Open SharePoint designer (https://www.microsoft.com/en-au/download/details.aspx?id=35491) and go to the site > All Files > Lists > ListName > Item.  In this folder you will see 2 XML files.   Export a copy of NFForm.xml. This is the current form that loads when you select new item. We will use the export of the file to import back into the designer in a later step. 2. The file that is loaded when you edit and save in the designer is found using a web browser at https://<tenanturl>/site/NintexFormXml  You will need to find the file that co

 When browsing to Nintex Forms for O365, a blank page logs with the following message:"An error occurred. Contact your site administrator to update the app." RESOLUTION:Configure your browser to allow Third-Party Cookies. For example, in Google Chrome: 1. Navigate to settings by selecting the ellipses on the top right the browser. 2. Select 'Privacy and security’3. Expand ‘Cookies and other site data’4. Check Allow all cookies.Error Code:"An error occurred. Contact your site administrator to update the app." Additional InformationIf using a macOS device (i.e. Macbook), you may need to also need to enable cookies in Safari > Settings > Privacy, even if you’re not using Safari. Cookies created by Nintex Forms for Office 365 are considered Third-Party Cookies. Enabling 'Block third-party Cookies' prevents a device from authenticating into SharePoint Online. This issue is not unique to certain operating systems or browsers as it can be replicated across various devices and browsers w

IssueA workflow suspends with the error "An authentication error has occurred.  The SharePoint Online URL does not correspond with the Destination site URL." when using an action that leverages one of the following two Connection types:SharePoint Online: Site & user administrationSharePoint Online: User management ResolutionVerify the setting for "Apps that don’t use modern authentication" is set to "Allow" in the SharePoint Online Admin Center (Access Control > Apps that don’t use modern authentication > Allow). If the action requires both the SharePoint Online URL and Destination Site URL, verify the URLs are from the same tenant. This could also indicate an intermittent connectivity issue.  Please reach out to Nintex Support if this occurs intermittently. Error Code"An authentication error has occurred.  The SharePoint Online URL does not correspond with the Destination site URL." Additional InformationThe SharePoint Online: Site & user administration and SharePoint On

IssueWhen opening a Nintex Form with a Lookup control, which allows multiple values from a Mac OS, it will render the Lookup control differently compared to the Windows OS.On the Windows OS, it will have two boxes with an arrow selection to choose multiple values and from the left box to right box.The Mac OS devices will render the Lookup control with only one box without any arrows to select the value and it will be moved from left side box to the right side box.   ResolutionChoose the multiple values in the lookup control by click Command + Click the value.  Additional InformationThe MacOs has a different way to render List Lookup control with multiple allow values allowed.  

IssueNumbers entered in Nintex form are being registered with comer in SharePoint when the Nintex form control is connected to a SharePoint column with the “Number” data typeThis is for all platforms of Nintex Form and SharePoint  ResolutionThis is a know issue in SharePoint, this is not a Nintex issue.There are workarounds1, Use a text column and not an number column data type2, Create a calculated column and use the formula = TEXT([Column Name], "0") 

ISSUEWorkflows are failing when attempting to run Office 365 Upload File Action. The workflow history shows the error: "An exception occurred while processing parameter [InputFileToUpload]."ERROR CODEAn exception occurred while processing parameter [InputFileToUpload]RESOLUTIONAdd one minute Pause action prior to the Office 365 Upload Document action.ADDITIONAL INFORMATIONThe pause action ensures that the workflow will not encounter a conflict when trying to interact with the document file within SharePoint Online.RELATED LINKS

IssueWhen using Nintex Forms Choice Control and creating rules that reference the choices, the rules do not properly respond when editing the form. ResolutionEnsure that the choice reference in the associated rule is the exact same string as the choice options listed in the control.  Additional InformationChoices: Sales, Marketing, IT, Support- Notice that there is a space after every comma, thus the rule needs to be written with the white space.Condition != 'Sales'Condition != ' Marketing'Condition != ' IT'Condition != ' Support'Choices: Sales,Marketing,IT,Support-Alternatively this is how rules should look with no white space in the choice control.Condition != 'Sales'Condition != 'Marketing'Condition != 'IT'Condition != 'Support' 

IssueA Send an Email action sent a blank email to the recipients when a workflow triggered by an imported workflow even though the body of the email has a text.  ResolutionRemove the current item reference in the email body. Re-insert the current item reference  Publish the workflow.  Additional InformationFor a workflow that has been imported from an exported workflow file, the Current Item: Insert References on the email body needs to be re-configured. 

IssueWhen trying to publish New Responsive Form in Nintex Form for Office 365, you might have the following error:"Something went wrong when publishing your form. Please retry again. " ResolutionVerify that the content type attached to the related List / Library is not Read only.  Additional InformationSteps to verify the Read-only setting for a content typeOpen List Settings. Enable content types if not enabled. Click on "Advanced settings". Select "Yes" for "Allow management of content types". Click Ok which will bring you back to List Settings. Click on the content type you are using for the form. Click on "Advanced settings". The value should be "No".Related Links  

IssueNintex Workflows will run even when all Start Options are disabled. ResolutionWorkflows require at least one Start Option selected when being published.  Leave "Start manually" set to active and navigate to List Settings > Workflow Settings > Remove, Block, or Restore a Workflow, find the workflow you want to not run, and make sure the No New Instances radio button is selected for that workflow. Additional InformationThe workflow will not run the first time it is published when nothing is selected, however if a start option was selected on a previous published instance, turning off the start options will not prevent it from running. SharePoint Designer workflows cannot even be published without a start option. 

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 open a Nintex Form for Office 365 (both Classic or Responsive), this error might occur:This site can't be reached ResolutionOpen the Nintex Form for Office 365 from a Private Browser. 

IssueAn Office 365 workflow becomes suspended and the only error message in the workflow history is 'Forbidden.'  ResolutionGrant access to write to the Workflow History list for the SharePoint site to the user account running the workflow. This will allow the workflow to display the true error which can then be used to resolve the underlying issue. Additional InformationWhen an O365 subscription has less than 30 days to the end of the subscription a message is written to the Workflow History list advising of this.This message is written using the permissions of the workflow Initiator.  If the workflow has an action set as the first action configured to run with elevated permissions the message will still be written with the Initiators account.  If the Initiator does not have access to the Workflow History list in this scenario the workflow will suspend with an access error.

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 using Office 365 Upload File action to update a Person or Group field, the following error occurs: ‘Error performing Office 365 upload file activity. Reason: There was a service parameter validation error. Error: Some parameters failed the validation check.Validation error 1 - InputMetaDataXml. Reason: The 'Fields' is invalid.’  Resolution'Office 365 Upload File' action does not support update to a 'Person or Group' fields. As a workaround, utilise the 'Office 365 update items' action to update 'Person or Group' fields. 

IssueWhen using "Send an Email" action with a user in Office 365, the following error is occurred : The message could not be delivered to one or more recipients ResolutionMake sure that the email is for a valid and active user.  Terminate and re-run the workflow. If the issue still persist, contact Nintex Support with the details of the email address, this will expedite the discovery of logs.  Additional InformationThe issue is intermittent and only occurs for periods of time.  The root cause is the email address has been soft blacklist by Nintex Mail Service, due to it previously attempting to send an email with an attachment that exceeded the size limit.  

ISSUEWhen trying to publish a Nintex workflow within Office 365, the workflow fails to publish and the following error occurs:Error publishing workflow. The request message is too big. The server does not allow messages larger than 2097152 bytes.ERROR CODERESOLUTIONRemove any unused actions within the workflow design. If there are no unused actions within the workflow design, the workflow will need to be split into multiple parts.ADDITIONAL INFORMATIONRELATED LINKSSplitting large or complex workflowsUpload large files sample add-in for SharePoint

IssueError "Unable to update XML. An error occurred while parsing EntityName. Line 1, position 116" occurs when updating XML by using Update XML action if the special characters such as an ampersand "&", less-than sign "<" or greater-than sign ">" are included. ResolutionEncode the special characters such as ampersand "&" to "&amp", less-than sign "<" to "<", greater-than sign ">" to ">". Error CodeUnable to update XML. An error occurred while parsing EntityName. Line 1, position 116 

IssueWhen using the action 'Get an Item from a Dictionary' inside the 'Loop N Times', to get each item within a dictionary variable, within in Nintex Workflow for Office 365. The workflow only returns the first value of the dictionary and ignores the remaining items.  ResolutionWhen referencing items in an array, use "(0)" for the first item, "(1)" for the second item, and so on.  For the 'Item name or path' field, of the workflow action 'Get an Item from a Dictionary', ensure that this field is configured with an 'index' variable used in the above point.  The index variable has to increment (+ 1) during each "for each loop" iteration Related LinksHelp file : Get an Item from a Dictionary  

ISSUEWhen running a workflow containing a Task action, the following error might occur:Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ArgumentException: AssignedTo at System.Activities.Statements.Throw.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation) Exception from activity Throw If Sequence NintexActivities.WorkflowXaml_{GUID} [Task action name] ERROR CODEDetails: An unhandled exception occurred during the execution of the workflow instance.  Exception details: System.ArgumentException: AssignedTo at System.Activities.Statements.Throw.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute(ActivityInst

ISSUEWhen responding to a task and updating the list item properties using Nintex Task Form for Office 365, the list item properties do not get updated.ERROR CODERESOLUTIONReset the Nintex Task Form.ADDITIONAL INFORMATIONThe issue is because the Form created by importing a List Form. RELATED LINKS