LM Tokens can they be broken down

I love this idea. However, posting it in the community, while it will gather support from other community members, will not likely get the attention of the product managers. You'll need to submit this through your portal under support >> contact support >> provide feedback.

That said, for a long time that system has been a black hole of ideas (ask any customer who has submitted feedback). There are glimmers of hope about some changes happening at LM that might change this, but I'll believe it when I see it.

Thanks and useful insight I have submitted some feedback lets see what happens. 

That said, the ##EXTERNALTICKETID## field is a list, not a string. So it would need to be something more like ##EXTERNALTICKETID.SERVICENOW.TICKET## or ##EXTERNALTICKETID.SERVICENOW.INTEGRATION##.

Being able to put have a display name shouldn't be part of the token, but part of the dashboard configuration. When adding the column, being able to put something like ##EXTERNALTICKETID.SERVICENOW.TICKET##Ticket No.## when adding the column would be great. That way the same field can have different names depending on where it's being used.

In the alerts panel, I can absolutely see ##externalticketid## and have access to my ConnectWise Manage tickets, but I can't do anything with that data anywhere else useful other than the CW integration and the Alerts page.  We drive alerts/ticket creations to Teams... and I can't include a link to the CW ticket in there, I can have a link to the alert, but that doesn't support our workflow.

This is something I've mentioned to LM quite a few times as our current number one missing piece.  ##externalticketid.<integrationName>## would be amazing.

UIv4 has a nice new column for the Incident.  It adds the incident number as a hyperlink to ServiceNOW.