Follow Us:
I’ve seen this come up here and there, and I wanted to try and jot down some clear steps. If you’re reading this then you likely have used the standard Issues list in SharePoint. It’s used for various purposes, but generally the out of the box provided ID column is used as the “Issue ID” since it auto-increments by default. While not configurable, it works for basic purposes. Invariably, users need to be notified whenever issues are created or updated, so they subscribe to alerts on the list. When they get their notification email, they notice that the Issue ID is missing, so they aren’t sure exactly which issue got updated.
We can fix this by adding the ID field to the email alert file. Unfortunately it’s not very straightforward or friendly to edit. But for this very small change, it works. This only works for SharePoint on-premise, you can’t do this with SharePoint Online. So if that's you, here’s what you need to do:
For alerts you get when issues are created, you will see the ID column but no value. I assume this is because the new ID value isn’t passed to the alert yet. But when you get an alert for edited issues, it should show the ID just fine.
A much easier possibility I tried was just to make a calculated column called like IssueID or Request ID, with a value of =[ID]. This worked once, but as soon as you edited an issue, the value would go to 0. So that didn’t work. Regardless, this works.
One slight variation on this is if you see on the changed alert email that the ID value is still blank, in the XML file around line 576 in the initial body tag, add the following:
<GetVar Name="NewValue#ID" />
This should load the value for the ID column.
For more information about C5 Insight or this blog entry, please Contact Us.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
Request Download
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.