Is there an efficient way to see the cause for "String or binary data would be truncated"?

This is a follow-up on this question . It is also related to this feature request from Microsoft. However, many years have passed and several major releases reached the market since it was reported. **Question:** does SQL Server 2017 provide any mechanism to ease finding out the root cause of this error? Or it is as hard to investigate as it was about 9 years ago when the issue was reported?