I encountered the issue mentioned on the following page:
I was trying to disable a save warning that was occurring on a secondary page that I was manually populating. I purposely de-selected all of the Set Component Changed fields on the page and even added hidden fields (eg. key fields) on the page so that I could de-select the Set Component Changed values for all of the fields in the record:
I managed to resolve this issue by following Dan Kibler’s advice in using the undocumented PeopleTools function SetSaveWarningFilter. SetSaveWarningFilter(True) disables the Save Warning while SetSaveWarningFilter(False) enables the Save Warning. I also managed to resolve this issue by setting to False the SetComponentChanged property of the rowset that was causing the issue.
As a general rule, I propose that if you know the rowset that is causing the issue then you should set the SetComponentChanged property to False since it makes for easier maintenance. The SetSaveWarningFilter option on the other hand, is more of a generic solution for cases where it’s difficult to find out exactly what is causing the issue.