Fixed bug that caused 404 when clicking "Back to Communication Records" #791 

~~Raising Http404 causes the "Back to Communication Records" button to break. If we can distinguish at which point non-integral values are returned for `record_id`, we can probably reintroduce Http404, but for now, redirecting to overview seemed like a safe way not to impact the user experience negatively.~~

Looks like this wasn't a regression, but rather the uncovering of a subtle pre-existing bug. Rather than reintroduce a redirect, I just call a different view function. Specifically, I called the same function that "Manage Records", which completely side-steps the issue. I'll be opening a separate issue for the fact that doing so doesn't retain date ranges. As the previous behavior was similar, this is not a regression.