I have a date field in a repeating section. To be able to use the date fields in emails or tables etc I have to:
For 99% of cases I have no problem, but for 1% of submissions, the same suspects over and over again, I have different results. To make is easy to compare the results to the steps above:
To rectify the situation I must open the form, save it, and restart the workflow. If I don't save the form again the issue persists.
Why does this happen for just some people and not others? In fact, why does this happen at all?
For #nintex365 #nintexonline
Solved! Go to Solution.
Thanks for the response. I thought I was going mad. Because we have offices around the world there is no way I can change the settings of each user profile to match.
For all those struggling this is my work around...
1. I create a conditional branch to see if the xml date field I'm looking at is of type DateTime. With the issues we're having it will either be of type DateTime (which documentation says it should be) or String.
2. If the xml field type is of DateTime I convert the value using Invariant as my regional settings, otherwise I use Default.
IIRC XStream is progressively centered around making whole item diagrams in one go - it's quite a while back that I last utilized XStream. Digester has a stack-situated Assignment Help | buyassignmentservice methodology which, in my psyche, loans itself fairly well to process extensive XML archives.