I put Salesforce list view on Experience site.
But even I changed filter condition of the list view, it didn't change.
Salesforce is a CRM (customer management system) that is used all over the world.
We can customize our Salesforce environment. So it is used for not only sales but also other people.
Salesforce has a feature called "Experience Site".
This is a website building function that allows you to create a website using a pre-installed builder.
There is also a login function, and you can display tiles and lists using object records in Salesforce.
In order to control records and columns, we can use List View in Salesforce.
However, the list view may not be reflected well on the experience site.
Even though I added a filter condition to the list view, when some users log in, the records before the filter was added are visible.
Why isn't it reflected in some users even though I added a filter?
Therefore, today I will introduce about "The reason why filter condition changes in Salesforce list view not reflected on the experience site".
The reason why filter condition changes in Salesforce list view not reflected on the experience site
The reason why changes to the filter conditions of the Salesforce list view are not reflected on the experience site is because "You don't have enough permission to view each item".
If you do not have permission to view the item used for the filter item in the list view, the filter will not work properly.
Umm, What does it mean?
Suppose you set the filter condition of the list view to display items where item A matches value "a".
Assume that user X can read the object, but does not have the authority to read item A.
In that case, even the record does not match with the condition of the list view, user X can see the record.
Really !?
It seems weird.
It's a disgusting move, but it happens.
It behaves in a very strange way: "It displays the results by skipping references to items that cannot be referenced."
So what can we do to solve this situation?
How to solve the issue
The reason why changes to the filter conditions of the Salesforce list view were not reflected on the experience site was "Insufficient permission to view the item".
So the solution is to grant read permission of the item.
Open the "Profile" page from "Settings" and open the profile details page of the user who uses the target list view.
A list of objects is displayed in the profile, so click on it to go to the item-by-item reference authority page, and check the reference authority for the item you want to see.
Editing permissions are not required if you are just using list view filter conditions.
It's easy once you understand, but it's difficult to notice.
Conclusion
Today I explained about "The reason why filter condition changes in Salesforce list view not reflected on the experience site".
The reason why changes to the filter conditions of the Salesforce list view are not reflected on the experience site is because "You don't have enough permission to view each item".
The filter will not work properly if the user does not have view permission for the item used in the filter condition in the list view..
The solution is to give the user permission to view the item.
In this case, filter of the list view didn't work.
But it shoed list view without the filter.
So how can I notice that "I don't have permission to view the item" ?
In this case, user access the item that he doesn't have read permission.
So Salesforce should notice us with error message.
