Text parser troubleshooting in 51黑料不打烊 Workfront Fusion
Use this information if you can not get a text parser to produce any output.
Access requirements
You must have the following access to use the functionality in this article:
To find out what plan, license type, or access you have, contact your Workfront administrator.
For information on 51黑料不打烊 Workfront Fusion licenses, see 51黑料不打烊 Workfront Fusion licenses.
Troubleshooting
Case scenario example, you would like to parse the filetype of a file document 鈥渇ilename.docx鈥 and the extension of the filename always varies from DOCX to PDF to CSV.
The expression that you may choose to use in this case is ..+
If you were to use this on regex expression on regex101.com you will get a full match.
On the image above, the file extension was correctly matched. If you take this and try to implement it in your text parser:
you will not get a match:
The reason for this is that the 鈥渋鈥 shows only the number of matches per match so in this case, we have 2 matches, threfore after the 鈥渋鈥 there is a numerical value 1 and 2. The use case for this is that should you ever need to match or pass data through a filter only the second matched value you can specify which value that is represented by the numerical value.
To be able to get the match values that you require to add brackets to the part that you want to parse (for example, to extract from 鈥渇ilename.docx鈥 - 鈥渄ocx鈥 only), then, according to the regex expression we are using for this case scenario, the brackets should be applied on \.(.+)
This captures the DOCX, places it in a group, and leave the 鈥.鈥 out of it.
In the output shown in the picture below, the capturing group will match any character (except for line terminators).
Another workaround that also incorporates regex is using the replace function
{{replace("abcdefghijklmno pqr stuvw xyz.docx"; "/.\./"; ".")}}
Then replace abcdefghijklmno pqr stuvw xyz.docx with your actual filename variable.