Archive: Nintex for Office 365 Knowledge Articles

IssueA trial customer that has paid the Office 365 subscription still have a trial notification when opening the Nintex Workflow or Form designer.  ResolutionThe licensing team has to generate a new license and to verify that the PPT ID must have a valid GUID format including dash symbol.  

IssueA '404' page error occurs when closing, submitting, or saving a Nintex Form. Resolution1. Open the form in the Nintex Form designer2. Open the settings for the button control.3. Navigate to Advanced > Redirect URL4. Ensure that the 'Redirect URL' is a valid address. Note: This field is blank by default. 

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' 

IssueAfter the license has been renewed, the Nintex Apps does not show up under App You Can Add in the all SharePoint Site within the tenancy.  ResolutionGo To SharePoint Store Search for Nintex Apps Click the button RENEW for the Nintex Apps in the SharePoint Store.  

IssueWhen tying to publish a workflow within Office 365, the designer presents the following error after selecting Publish:Error publishing workflow. System.Net.WebExeption: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. Error CodeError publishing workflow. System.Net.WebException: The underlying connection was closed: A connection that was expected to be kept alive was closed by the server. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.EndRead(IAsyncResult asyncResult) --- End of inner exception stack trace - ResolutionOption 1:If the site was recently migrated, please remigrate the site and that should resolve the issue.Option 2:If the site was not recently migrated, please contact M

IssueWhen submitting a Responsive Form in Office 365 using Google Chrome, the following error is presented: Resolution-Evaluate your controls that render as drop down lists-Ensure that there are no 'white spaces' following any of the choices available in this drop-down list Error CodeInvalid postback or callback argument. 

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. 

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

IssueNintex Task Form for Office 365 does not show the list item details for the record inside the Repeating section control.  ResolutionVerify the control name inside the Repeating section to make sure that the control name is exactly the same between the Nintex List Form and Nintex Task Form.  

IssueWhen responding to a Task in Nintex Workflow for Office 365, the following error may occur: Invalid text value. A text field contains invalid data ResolutionVerify that the approver comment contains less than 256 characters.  Add validation to Nintex Task Form to set the maximum character up to 255.  

IssueWhen trying to add one of the Nintex for Office 365 apps to a SharePoint site, the app addition fails and the following error occurs:Something went wrong trying to add app. Click to retry. When trying again, the app addition fails again with the same error. ResolutionContact SharePoint Online support and request to have the app site manually cleared from Azure. 

IssueWhen using certain Nintex Forms controls, i.e "People Picker", you may observe the following error:“There are unresolved entries”  ResolutionThis occurs when you are using a non-English regional setting, and is a known behaviour. We request users to vote for this change to be implemented via the below link:https://nintex.uservoice.com/forums/218293-4-nintex-forms-for-office-365/suggestions/31337908-missing-auto-generated-translations Additional Information  Related Links  

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.  

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. 

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 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.  

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 

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.  

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. 

ISSUEWhen publishing a workflow, the following error might occur:Error publishing workflow. Workflow XAML failed validation due to the following errors: The private implementation of activity '1: DynamicActivity' has the following validation error: Value for a required activity argument 'TargetListId' was not supplied. HTTP headers received from the serverERROR CODEError publishing workflow. Workflow XAML failed validation due to the following errors: The private implementation of activity '1: DynamicActivity' has the following validation error: Value for a required activity argument 'TargetListId' was not supplied. HTTP headers received from the serverRESOLUTIONRecreate the Query List actions in the workflow. Republish workflow.ADDITIONAL INFORMATIONRELATED LINKS

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