We have the following two custom fields (Type__c and Area__c) in Case Standard object.
While resolving an issue, I found out that the field dependency between Type__c and Area__c has been updated by user.
Please see below.
Now I asked the user as to why he made the change and was told that he never made any changes and even does not know about field dependencies in the first place.
Then I did some research online and found this article.
As per this article this field dependency timestamp showing as an user (who does not have "Customize Application") is working as expected and can happen because of the following reasons.
Some other examples of places that could update the picklist_set table are as follows:
When the field dependency is modified When the picklist field is modified When a picklist value on a picklist field is modified When cPicklist.picklist_update_time_nco, cPicklist.picklistset_ups_nocheck_nco is called.
But as per the user he has not made any changes at all with respect to Type__c & Area__c.
Can someone tell me if they have faced any situations like these or are there any actions that the user would have taken inadvertently that would have caused his login to be timestamped ?