That's what I suspected. So, we've decided to workaround this issue using static data linking, but it is not ideal. Here's our proposed solution:
Each dev would have two databases linked to our DB in source control. One for developing our software and mucking around with the database. The other for committing schema, and static data changes. We would never commit anything through the first DB, but rather use the "Get Latest" periodically to reset the DB state to what's in source control. The latter would be used to commit schema/data changes as desired and would essentially serve as a master copy of our source-controlled DB.
I think this will work for us, but it's a bit annoying. Hopefully you will have some improvements in the software down the road to manage data a bit better. If you can think of a better workflow, I'm all ears.