We have a system view that when I view it's fetch xml representation links 2 entities. In outlook users are using that view and adding one filter. When attempting to save the updated filtered view an error such as below is generated.
The view being used uses the activity entity and looks for all activities where activity states = open
and activity type is any type of activity (ie task, email, etc).
The resulting view includes columns from one other related entity and some of those are lookups (ex - the manager of the related record for example).
Running a view like this in the UI poses no problems. The issue only occurs when trying to add one more filter - in this case Where owner = some user and saving the filter in Outlook.
Even if we remove the filter and simply try to save the view as is in Outlook this error occurs.
Is there a difference in the way views in Outlook vs the UI are handled? If the view is using lookups from one related entity in the display columns , could that be an increase in the link entities count?
Robert
