I have a Nintex workflow for a SharePoint 2013 list. The list has a "Due Date" date column and an "FY" calculated column. FY calculates the Fiscal Year from Due Date. When I run the workflow on an existing item, FY is present and the workflow works as designed. But when I run the workflow automatically on a new item, FY has not been set, and the code fails.
Is this typical behavior? Would it be best to pause the workflow until FY has been populated before proceeding? Since the workflow fires after the save, I'm not sure why the calculated column is not already populated.
Solved
Workflow does not show calculated column for new item
Best answer by Michel
It can happen that the calculated value is not present as soon as the workflow starts, as you already suggests. You could add a pause/wait to the workflow, but you could also calculate the FY within the workflow. Would that work in your situation?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.