Incorrect Salesforce List View Loads Due to Possible Existing Duplicate List Views

Salesforce identifies every list view by an API name or devname that’s different from the list view name that you see on your object page. So that Salesforce can tell one list view apart from another list view, every list view needs a unique API name. In some cases, however, two different list views incorrectly share the same API name.
When this happens, if you select either of the affected list views, you see the list view that is most private to you. For example, if one of the list views is custom to your user profile and the other is a public list view, you see the records for the private list view.

Duplicated API names for list views can occur in a variety of scenarios, such as when you import a managed package that includes a modified default list view. For example, let’s say that you have the default list view, All Work Orders, and you make edits to that list view. Then you export a managed package that includes the modified All Work Orders list view, and import the managed package into a target org that already has a default All Work Orders list view. The target org can end up with two different versions of the All Work Orders list view that share the same API name. To help prevent this situation, we generally discourage including default list views in exported packages.

To resolve a duplicate list views issue, clone the affected list view to make a copy, and then delete the original list view that you cloned. The new copy of the list view automatically has a unique API name, so you can select either the new list view or the list view that was inaccessible previously.

Resolve From the List Views Page

• From the List View Controls menu, click Clone.
• Give your list view a name and select who can see the list view.
• Make sure the name is distinguishable from the list view that you cloned. Remember that you can edit the list view name later if needed.
• Save your work.
• Click the list views dropdown menu and select the list view from which you created the clone.
• From the List View Controls menu, click Delete and then Delete again.

Resolve From API

Note: API doesn’t support cloning a list view. If you delete a list view through the API, you must manually replicate it. We recommend that you resolve this issue from the List Views page instead.

• To remove the most private of the affected list views, call DELETE on the /list-info endpoint.
• To recreate the delete list view with a different API name, call POST on the /list-info endpoint