Using Item Properties from Insert Reference Issue

Hi Suzanne,

How are you setting the start date on the list item?  Is this via a default value or something else?

Cheers,

Chris

Hi Suanne,

The way you are setting up the start date here will just give you a blank start date.  The default value at this step does not really matter.  Does the start date get changed before the email is sent?  Where do you set the value for the start date field?  Is it filled in by a users? Or by the workflow itself?

Regards,

Francois

Hi Suzanne,

It sounds like the Start date is linked to the action date for some reason. In Nintex you have the option to link a variable to the action execution date or today which sounds somewhat like your scenario.   Can you double-check this?

Can you send a screenshot of where you put the start date into the email?

Thanks Suzanne,

Can you also send a screenshot of where you set it up in the workflow?  With all the {startdate} variables in the email.

Hi Suzanne,

It looks like something is modifying the start date because the screen shots that you've provided look OK.  It's very strange that someone enters 23 May and the email says 4 April.  If they were one day apart then I'd be looking to investigate timezone/daylight savings issues.  e.g. if the user is in a different part of the world to the server etc.  However a date that's 40+ days apart is not that (I checked to see if it was 45 days apart but it wasn't).

So, can you do a few things:

1. Go to the SharePoint list and see what start date is displaying for that same item you've listed above.  Temporarily modify the view to show the column if it isn't being displayed.  This will tell us if the date has been changed somehow.  If it is displaying as 23 May then we have further work to do
2. If the date is 4 April then you'll need to look through the form first.  Is that changing the date somehow?  Best way to test is to have someone fill in and save the form and check what the date says.  Do not have any workflow kick off automatically just in case it's the workflow that modifies the date.
3. If the form doesn't change the date to 4 April then it's time to look through your workflow from the start to see if you're manipulating the date somehow (e.g. update item) or is there a different workflow that's doing this?  The clue might be in your 45 day start - was there anything that attempted to calculate that date?

Cheers,

Chris

Hello Chris,

1. on the list for the screenshot above the list is showing 5/23/16 - 5/27/16

2. Created new request, date did not change once the user submitted.

3. I will test the newly created request to see if the date changes.  The workflow is manually started.  I kickoff the workflows 45 days prior to the start date of the travel.

Thanks,

Suzanne

Hi Suzanne,

just a quick check..are you sure that the StartDate reference you are using in the notification is the ItemProperty and not the reference with the same name under common tab?

you can check in the html of the mail, if the reference is Common:StartDate then you are using the wrong reference..

Giacomo

Hello,

Dates on Original list request submitted.

According to the Workflow History that I can see the date did not change.

Is there another workflow history I can check?

Thanks - Suzanne

Also the approval e-mail notification still has the incorrect date.  It is using yesterdays date, even though it was created 4/7 and approved on 4/7.

If you try to insert a new reference to Start Date, is it created with reference to common variable?

If not, you can try to add a set Variable in your workflow to set an existing variable to your Start Date field, then if you go with the mouse over it you should see on the tooltip something like {ItemProperty:FieldName}

This is to check if SharePoint has putted in some strange characters in the fieldname, once you have done that, you can delete the set variable and you edit your html replacing the common%3AStartDate with ItemProperty%3AFieldName

I wonder if this is a bug and something to do with the fact you have a column name the same as one of the reserved field names.  Would you mind please logging a support call for this Suzanne so the Nintex engineers can investigate?

Cheers,

Chris