# Parse a string with special characters

**URL:** <https://community.dynatrace.com/t/parse-a-string-with-special-characters/56884>\
**Category:** DQL\
**Tags:** dql, parse\
**Created:** [September 4, 2026, 1:37pm UTC](https://community.dynatrace.com/t/parse-a-string-with-special-characters/56884 "2026-09-04T13:37:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![slhempen](https://avatars.discourse-cdn.com/v4/letter/s/3ec8ea/32.png) [@slhempen](https://community.dynatrace.com/u/slhempen)\
**Post date:** [September 4, 2026, 1:37pm UTC](https://community.dynatrace.com/t/parse-a-string-with-special-characters/56884/1 "2026-09-04T13:37:35Z")

</div>

I have this string in a message field that needs to be parsed.&nbsp; I need the values between the double quotes extracted into separate fields.&nbsp; I am having a hard time getting the correct syntax to handle eliminating ‘\<’, ‘/\>’, and ‘"’.

\<Robotics UseCase=“UC987” Workstation=“WTWABCDE” UserID=“xxxx” Department=“HR” Segment=“Express” Automation=“GetConfigData” MessageType=“Failure” Message=“Subflow: GetConfigData, Action: 28, Action name: Set variable; Variable ‘Config\_Global’ doesn’t have a property ‘LogSegment’.” ClaimNumber=“1345089A5” TaskID=“” /\>

Thanks,

Steve

---

<div class="post-metadata">

**Author:** ![dannemca](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dannemca/32/7215_2.png) [@dannemca](https://community.dynatrace.com/u/dannemca)\
**Post date:** [September 4, 2026, 2:30pm UTC](https://community.dynatrace.com/t/parse-a-string-with-special-characters/56884/2 "2026-09-04T14:30:00Z")

</div>

A very simple parsing would be:

```markup
LD 'Robotics UseCase="' LD:RoboticUseCase '"' LD 'Workstation="' LD:Workstation '"' LD 'UserID="' LD:UserID '"' LD 'Department="' LD:Department '"' LD 'Segment="' LD:Segment '"' LD 'Automation="' LD:Automation
'"' LD 'MessageType="' LD:MessageType '"' LD 'Message="' LD:Message '"' LD 'ClaimNumber="' LD:ClaimNumber '"' LD 'TaskID="' LD

```

The only field not able to include in the above parsing rule was the TaskID since empty, and will requires a different parsing rule.

Try and let us know.
