Updating Phone for User is not causing OneRoster to update dateLastModified

@Tim Harris
Going to need some Blackbaud folks in community to better answer this, but my 2cents:

Currently Blackbaud does not really have a good documentation on what causes a record's last modified field to change, we as client have to “guess and test” to know. There's an idea out in IdeaBank for BB to better document this.

Your issue is like the same as a Constituent record situation. Back in “database view”, when you update address, phone, email, constituent code, constituent attribute, the constituent record itself will be “updated” (the save and close is in the constituent record level).

However, in NXT webview and SKY API, this changes. “pieces” of information of a constituent can be changed without “changing” the constituent record itself. Constituent code can be added/updated/deleted and not have the constituent record marked as changed/last modified. Same with attribute/custom fields. I believe also same with phone and email. This is quite unforunate to have to “guess and test" to know for sure. I hope BB give the idea of better documentation some resource hours relating to “last change” and list API.