Argument not valid when lookup field is used in a view

(0) Share

Report

Posted on by Xavier Villafuerte

352

Hi, we found the following weird scenario in a Microsoft Dynamics CRM 2016 8.1 OnPremise deployment. We have views for Opportunities which uses the Account lookup field as one of its columns. With some frequency, users of those fields report they got an "Argument not valid" error when executing any of those views. What we found is the problem occurs only when the Account lookup field is included as a column; if we replaced it by the Account Name (which is a text field) everything works fine always.

We suspect some kind of data corruption in the Account Entity but we have no idea about how to identify the data corruption pattern which causes the problem. Information in that entity is being replicated from an external system.

Do you have any advise about how to troubleshoot this issue? Any advise is much appreciated.

Xavier

*This post is locked for comments

I have the same question (0)