Updating Phone for User is not causing OneRoster to update dateLastModified

Tim Harris

I'm working on an integration via OneRoster with Blackbaud and playing in the SKY Developer Cohort. While grabbing info via Postman, I noticed that updating a User's name or email updates the ‘dateLastModified’ value in OneRoster, but any updates to Phones is not updating this field.

We're currently looking to this field to determine if we need to grab updates to the User profile so we aren't getting Phone updates (unless other updates are also made). Does anyone know why updating the Phone info wouldn't update this ‘dateLastModified’ field?

Alex Wong

@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.