Archive: Nintex for Office 365 Knowledge Articles

IssueWhen using Print to PDF in Nintex Form for Office 365 that has an Image, the PDF output does not display the image.  ResolutionVerify that the Image location is in the same Site Collection.  

IssueWhen sending emails using the Send An Email action in an Office 365 workflow, the emails have a blank subject line when received by recipients. ResolutionWhen using an Advanced Lookup within the subject line field, do not copy and paste them from one Send An Email action to another. Re-type the subject line and re-use the Advanced Lookup control to pull in the lookup value. 

IssueThe conditional criteria, for a conditional start workflow are no longer visible from the workflow setting. This occurs after the Workflow designer is reopened, after modifying the conditional criteria.   ResolutionThe issue has been fixed on the latest version of Nintex Workflow for Office 365 Apps that was released on 21th November 2018. Make sure that the site has the latest version of Nintex Apps 

IssueWhen using the Task action in Nintex Workflow for Office 365 with the "Auto-complete task" setting being activated, the user finds the "task date completed" is the same date when the task created, this can be confusing as to when the Task was actually completed.  ResolutionMake sure to get the information on the task last date modified from the task itself (via workflow task list) and not from the item related to the task.  Additional InformationUse the Query List action by supplying the Task ID from the Task action output, to get the information details of the completed Task. 

IssueWhen trying to use the "Calculated value" control with the fn-Replace function, in the following format: ("textToModify", "replacePattern", "replacement") The result will be different from the one expected. ResolutionResolution:Remove the two quotations that were placed around the 'TextToModify' parameter so that it should be in this format: (textToModify, "replacePattern", "replacement") 

IssueWhen adding Nintex Workflow or Nintex Forms for Office 365 apps to a site, they show as "Pending Purchase" instead of being added to Site Contents. ResolutionThe apps are pending approval within the SharePoint Online environment and must be approved by the SharePoint tenant administrator. For more information, see Request app installation permissions in Microsoft Support.  

IssueWhen an external email address is configured in a Assign a Task workflow action, the following error occurs:Sorry, we're having trouble reaching the server  ResolutionConfigure the Assign a Task action with an email address within the Office 365 tenancy. Additional InformationEmail recipients in Assign a Task action are restricted to those with email accounts in the Office 365 tenancy. Related LinksHelp File - Assign a Task 

IssueWhen publishing a workflow, the following error might occur:Error publishing workflow. Workflow XAML failed validation due to the following errors: Activity 'FormatString' has XX arguments, which exceeds the maximum number of arguments per activity (50). Activity `FormatString` has 59 arguments, which exceeds the maximum number of arguments per activity (50). (...). The remote server returned an error: (400) Bad Request. ResolutionReduce the number of field entries to be render into and the error should disappear and the publish should work.  Additional InformationSharePoint Workflow Manager has a limitation of 50 references for a 'FormatString' Activity. This can surface either in Log to History Actions (if the character limitation is not reached first) or by trying to render those in an action such as a "Send Email" or "Assign Task". 

IssueWhen trying to export a Nintex Workflow or Form a dialog appears with the error Export Fail.  ResolutionIncrease the Site storage limit and try again. Error CodeExport Fail Related LinksManage site storage Limits : Manage site storage limits 

IssueWhen using the Assign a Task action, the workflow automatically suspends if a external email address is used. ResolutionThis is by design. Email recipients are restricted to those with email accounts in the Office 365 Tenancy. For more information, see Office 365 Assign a task action. 

ISSUEResponsive form does not appear in Nintex Mobile.ERROR CODE RESOLUTIONOpen Nintex Forms for Office 365 app from the list ribbon and click on the Nintex Forms settings. Under the Nintex Mobile Settings and enable "Publish to Nintex Mobile (iOS and Android)" checkbox.ADDITIONAL INFORMATIONRELATED LINKS

IssueOnce a modified item form has been submitted, a child workflow starts before a parent workflow begins and displays the following message: A workflow is currently running. Please wait for it to complete. ResolutionManually terminate the running workflow instance and re-run the workflow.  

IssueList lookup() runtime function does not return any results on Nintex Mobile form. ResolutionThis is expected behavior.The List Lookup control is compatible with Nintex Mobile but the Lookup() runtime function is not compatible. 

IssueWhen a Nintex for Office 365 workflow configured with one of the Office 365 workflow actions runs (such as Office 365 Query User Profile), the workflow suspends with the error 'The username is invalid or does not exist, or the password is invalid for the username specified' in the workflow history. ResolutionEnsure that the credentials used in the Connection are correct. Connections can be found under Site Contents > Nintex Workflow for Office 365 > Connections Note: Credentials aren’t validated when the Connection is saved. When in doubt, attempt to login to your SharePoint Online tenant using the credentials in question to confirm that the credentials are valid. Verify that the account being used does not have Multi-Factor Authentication (MFA) enabled, as MFA is not currently supported by Nintex for Office 365. Note: MFA only impacts Connection types using Basic authentication. Connection types using the OAuth 2.0 authentication method shouldn’t be impacted by MFA. Speci

IssueWhen trying to publish the Form, this error might occurs:Failed to Publish. ResolutionNavigate to Nintex Form hidden library. https://SiteURL/NintexFormXML/ Verify that all the files here has been checked in. If there are files has been checked out, then it needs to be check in.  Resolve the error during the check in (if any). Possible error during the check in:Sorry, something went wrongYou must fill out all required properties before checking in this document. Those error above indicating there some required additional field that does not created by Nintex has been added to the Nintex Form hidden library. As resolution, go to the Library setting and set to No for the required fields.  

ISSUE After installing the Nintex Document Tagger Add-in, the following error message occurs when opening the add-in:Your System Administrator Has Blocked Add-ins From The Office Store. RESOLUTION Update Active Directory Group Policy to allow add-ins for Office applications. ADDITIONAL INFORMATION This restriction is managed by internal IT teams. For more information reach out to Microsoft Support.

IssueCannot see the Nintex Workflow or Nintex Forms for Office 365 app within Site Contents even after adding the app to the tenant from the SharePoint Online store. ResolutionOpen Office 365 Admin panel Open SharePoint Online Administration Open the Apps menu Open Mange Licenses Select the drop-down arrow next to the Nintex Workflow for Office 365 or Nintex Forms for Office 365 section, and select Manage License Select the ACTIONS control drop down and select Recover License Select Continue and then Return to Site 

IssueWhen using Document Generation action in a workflow the following error is produced:An error occurred downloading a file from a URL (https://Tenant-Name.blob.core.windows.net/docgen ....) Error Code RequestorId: aa5eeb05-22ff-78a5-0000-000000000000. Details: An error occurred downloading a file from a URL (https://tenant.blob.core.windows.net/........). (ResourceInvalid) (ErrorId: dea86c39-aaaa-44e7-ab55-7b9e715ebff3) Resolution - Ensure that the Output filename field does not contain special characters in the Document Generation action settings.- If using a workflow variable or a reference, ensure that value is clear from any special characters. Additional Information When using a workflow variable or a reference like "Username" or "URL" as the output file name, the action will fail to generate the document due to the fact that the name includes special characters in the value of the filename. 

ISSUEWhen adding the Nintex Workflow for Office 365 app, the following error occurs:Sorry, this app is not supported on your serverERROR CODE"Sorry, this app is not supported on your server"RESOLUTIONNavigate to:  https://<YourTenantName>-admin.sharepoint.com/_layouts/15/online/TenantSettings.aspx Scroll down to "Connected Services" Uncheck the "Block SharePoint 2013 workflows" box. Click OK to save changes.ADDITIONAL INFORMATIONRELATED LINKS

Issue When using LazyApproval with Nintex for Office 365, if the task assignee has an 'out of office' response, the LazyApproval system sends a second email saying that their response was not valid.    Resolution This is currently expected behavior within Office 365, as LazyApproval within Office 365 currently does not support LazyApproval. There is a feature request for this functionality which can be found here.  

ISSUEWhen accessing workflows in Office 365, the following error might occur: Some workflows may not be shown. We are unable to reach the workflow service ERROR CODESome workflows may not be shown. We are unable to reach the workflow serviceRESOLUTIONContact Microsoft to verify the Workflow Manager service is functioning correctly.ADDITIONAL INFORMATIONRELATED LINKS

Issue Office 365 Nintex workflows are triggering multiple instances.   Resolution Open 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 clicking on a task link from a mobile device the task may open up in a browser depending on associations on the device.If the task opens in a browser a SharePoint task form will be presented in either View or Edit mode regardless if a Nintex Responsive form has been added to the task or the appropriate layout has been added to a Nintex classic Form.  ResolutionThe SharePoint Task form showing is not a bug but a limitation. Additional InformationA workaround for this issue is to insert a custom link in the email notification.Click "Link" from the Insert tab ribbon and add a custom link as per the example below.fn-Replace("{Common:ApprovalUrl}", "Lists/Workflow%20Tasks", "_layouts/15/NintexForms/Mobile")&List=<TaskListId>Note: Change Workflow%20Tasks to your Task Name and <TaskListId> to your task list id GUID.The idea for this approach is to use Approval Url which is similar to <SiteURL>/Lists/Work

ISSUEWhen running the 'Delete Item' action via the Workflow 2013 Engine office 365, the deleted item does not go to the recycle bin.ERROR CODERESOLUTIONThe 'Delete Item' action is functioning as intended, the action utilized by Nintex is the same as used in SharePoint Designer. In both cases the delete item action for the 2013 engine does not send the deleted item to the recycle bin.  It is possible to utilize the 'Office 365 Delete Items' action to delete items that are sent to the recycle bin. For more information, see Delete items. This action runs outside of the tenancy will take a bit longer as result. ADDITIONAL INFORMATIONRELATED LINKS

Issue"Access denied: Connection does not have access error" when configuring an action using a Connection in Office 365. Error Code"Access denied: Connection does not have access error" Resolution Connection type Minimum permissions SharePoint Online: List & library SharePoint - Designer SharePoint Online: Site & user administration Full SharePoint Online: Site collection administration SharePoint - Global admin SharePoint Online: User management SharePoint - Global admin Nintex Connector - Azure Directory Admin consent required Azure AD app permissions: Read all user's full profile Read all user's basic profile' Nintex Connector - Azure Directory Administration Admin consent required Azure AD admin account required to make connection Azure AD app permissions: Read and write all users profile Read and write directory data  Additional InformationThis table is summarized fo