Archive: Nintex for Office 365 Knowledge Articles

IssueWhen using "Office 365 upload file" action and the file name contains a special character such as {} ~, the following error may occur: Some parameters failed the validation check. - [InputDestinationFileName] : The file name is invalid. ResolutionThis issue has been fixed on the latest version of Nintex Workflow for Office 365.  

IssueWhen configuring the Document Generation action, the configuration indicates the document quota has been exceeded, even when no documents have been created. ResolutionContact Sales@Nintex.com. Have Sales verify that the 'Nintex for Office 365' asset and 'Nintex Document Generation' asset are active. If both assets are active, confirm that both assets are on the same contract. Even if both assets are created and live, if they're on separate Salesforce contracts, Document Generation for Office 365 will not work.   Additional InformationThis is caused by a mismatch in the licensing with the associated customer account.Looking at the JSON call that is made when the action configuration loads, you will see the following inside of developer tools: {"Total":0,"Used":0,"IsTrial":false,"SubscriptionStartDate":"0001-01-01T00:00:00","SubscriptionEndDate":"0001-01-01T00:00:00","OverUsage":0,"QuotaOverageAllowance":0,"ErrorType":400,"IsSuccess":false,"ErrorPayload":null,"Info":null,"Subscripti

IssueWorkflow suspends with the below internal error.Error: Document generation error: Processing error. Failed to process image data Error CodeDocument generation error: Processing error. Failed to process image data ResolutionSolution 1:Specify the absolute image urlSolution 2:Reference a column that is not of type 'Hyperlink or Picture' and use a single line of text column instead.

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.  

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 a 'Calculated value' control with a decimal number, in Nintex Forms for Office 365, the control is removing the number after the decimal separator. For example: The expected value : 1000,45 The result value : 100045 ResolutionChange the control setting of 'Calculated value' of the 'Save as data type' from 'General' to 'Decimal' 

IssueWhen running a workflow that includes a Send an Email action, the workflow will complete successfully, however emails are sent intermittently. ResolutionOpen a support ticket with Microsoft SharePoint support with the Workflow Instance ID of one affected workflow, along with the Start Time and Last Run Time from the Workflow Status page of the instance.  Additional InformationSharePoint Online handles the mail flow for internal emails, as such Nintex does not have any control of email delivery while workflows use the internal mail system of Office 365. 

When a task assignee attempts to respond to a task using LazyApproval, the response is not accepted.ConditionsCustom HTML is applied to Initial Task Notification in 'Assign a Task' HTML includes a <Title> element LazyApproval is enabled Additional InformationThis behavior is caused by the email client through which the response was sent. For example, Outlook in Office 365 ignores the <title> tag, however, the Outlook Desktop Application will include the <title> tag in your response, forcing LazyApproval to process and reject the contents of <title> as a response.  

Issue When creating a Excel Spreadsheet, using a Create List Item action, the Excel spreadsheet does not open, and shows the error:"We are sorry, we could not open your workbook. It's possibly corrupt or using a file format that is not supported."  ResolutionThis is an underlying issue with the Sharepoint platform and also occurs with a Sharepoint Designer Workflow action: "Create List Item"As an alternative, use the O365 action “Office 365 Upload File" 

Issue When using Office 365 update Item Permission action, it give an output of the List item URL that can not be use afterward. The URL format return by the List item URL as below: ["https://site_url/Lists/list_name/DispForm.aspx?id=2"]    Resolution Convert the List item URL that has a Collection data type into single text by utilize action "Get Item From Collection".    Additional Information The details of "Get Item From Collection" can be found here.   Related Links Help file "Get Item From Collection"  

IssueOffice 365 Nintex workflows are triggering multiple instances. ResolutionOpen the Nintex workflow causing issues in the Nintex Workflow designer. Navigate to the workflow settings in the designer ribbon and check the workflow start conditions. It possible the workflow is configured to start when a item is updated or when a specific condition is met. The workflow is most likely meeting multiple start conditions, causing the workflow to trigger more then once. Example: The workflow is configured to start when a item is created or modified. The workflow starts and the first action performs an update to the current item. The update causes the workflow to start again based on the workflow start conditions. The workflow start conditions need to be adjusted or the workflow design changed. 

IssueWhen using the Create List Item action, workflows that are set to start on Item Creation are not started on these items. ResolutionThis is expected behavior with SharePoint 2013 (Workflow Manager) workflows. As a workaround, use the Office 365 Create List Item or Document Set action. 

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") 

ISSUEWhen accessing a Nintex form, the following error occurs:Unable to get property 'value' of undefined or null reference FormsPart.aspxERROR CODERESOLUTIONIn the FormPart.aspx JavaScript to get the value from the single line textbox control, locate the following line of code:NWF$(".option_crId_control .nf-filler-control-inner")[0].firstChild.dataAnd update it as follows:NWF$(".option_crId_control .nf-hidden-associated-control").val()ADDITIONAL INFORMATIONRELATED LINKS

IssueWhen using an action in Nintex Workflow for Office 365 that utilize Connection Manager, this error might occur:Identity Client Runtime library (IDCRL) encounterdd an error while talking the partner STS ResolutionReset the password of the account credentials of the Connection Manager.  Additional InformationThe password of the account that is used on Connection Manager has expired.This happened even for the account that has been set to password never expires.  

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 creating a save button in a task form, the button cannot be used without one of the task outcomes being selected.ERROR CODERESOLUTIONThis is expected behavior. As a workaround, try the following:Create an additional outcome (Incomplete or In Progress etc). Set the new outcome as the default value for the outcome control Create a hide / disable rule on the 'Save & Submit' button for when the outcome is equal to the value created earlier. For example: taskoutcome=="Incomplete" This would allow the save button to be used, but would prevent anyone from submitting the form until the outcome field has been set to one of the expected out of the box fieldsADDITIONAL INFORMATIONRELATED LINKSHow to ignore Decision validation when save button clicked in Flexi Task Nintex Form

IssueWhen using Send Email action, emails are not being delivered. ResolutionCheck the Clutter/Junk mailbox and mark the email as 'Not as Spam' Additional InformationIt would also be a good idea to add the following emails to the address book:no-reply@sharepointonline.comnoreply@workflownotification.com 

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 using action Office 365 update item permission, this error might occurs:Failed to resolve group <group name>  ResolutionVerify the group is exist in SharePoint Online.   Modify the action with a valid group name. Terminate and start a new workflow instance.  

IssueWhen using Office 365 query user profile action with connection manager, this error might occur:Unable to reach destination server ResolutionEnsure that "workflows can use app permission" feature has been activated via site settings >> Manage site features If MFA (Multi-factor authentication) has been enabled in tenant then execute the cmdlet Set-SPOTenant -LegacyAuthProtocolsEnabled $true Additional InformationSet-SPOTenant - https://docs.microsoft.com/en-us/powershell/module/sharepoint-online/Set-SPOTenant?view=sharepoint-ps 

IssueEven though reminders have been set for Start a Task Process action, the notifications are not being receive. ResolutionTo receive task reminders with Nintex Workflow for Office 365, you need to set the Due Date within the action configuration. If the Due Date is blank the reminders will not be sent as the workflow wouldn't know when the Task is due is actually due. Additional InformationYou can read further information and the Task action configuration options in the the help file below.Start a Task Process 

IssueWhen running Nintex Workflow for Office 365, the following message appears in the Workflow status history page:The list '{Workflow Context:List Name}' does not exist in the web site ResolutionThe error is shown when the 'List name' field has either been entered in manually or copied and pasted from a similar account. To resolve the issue, you will need to do the following:1. Open the Workflow Designer2. Open the Office 365 Live action3. Clear the existing field for 'List name'4. Place cursor in the 'List name' field5. Expand 'Workflow Context' section on the right6. Click on 'List Name' to add this information to the 'List name' field 

ISSUEWhen running a workflow that is configured to send an email, the workflow suspends with the following error: RequestorId: 6fdb72dd-529e-e60f-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 400 {"error":{"code":"-2130242040, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"The e-mail message cannot be sent. Make sure the e-mail has a valid recipient."}}}ERROR CODERequestorId: 6fdb72dd-529e-e60f-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.ApplicationException: HTTP 400 {"error":{"code":"-2130242040, Microsoft.SharePoint.SPException","message":{"lang":"en-US","value":"The e-mail message cannot be sent. Make sure the e-mail has a valid recipient."}}}RESOLUTIONWhen trying to send to an email that is not associated with an account within SharePoint Online, ensure that t

Issue Numbers 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    Resolution This 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")