I am guessing there is a simple way to do this but I am missing it. My pattern matching output is giving me a date string of \d\d\d\d\d\d\d\d ex: 01012014 for Month/Day/Year. The field rejects the value without the forward slashes. It is a date field. Dashes work until there is not capture value. Is there a simple way to get the forward slashes into the input string? Would a token or substitution work in this case? Thank you.
Question
Question
Answer
Hi Seth,
You've pretty much got it! A substitution should do exactly what you need. You'll want to use the token for your date pattern matching as the input for the substitution. Then, using your examples, your substitution can look something like this:
Basically you'll tell Quick Fields to isolate the results of your pattern matching into three groups, each one indicated by a set of parentheses. Then, in the "With" section of the substitution, you'll just tell it to add a forward slash between each group it finds.
If there's a possibility that your input will already have forward slashes, that can be accommodated too by adding /? between each of your sets of parentheses in the "Replace" section of the substitution.
Once you've got your substitution set up you'll use this activity's token to populate your date field rather than the pattern matching activity's date token.
Replies
Also, if your question has been answered, please click the "This answered my question" button on the response.
If you still need assistance with this matter, just update this thread. Thanks!
Hi...I'm trying this and it is not being accepted in my Date field. I only have six digits total. Please help!