It depends.  In some circumstances you may have to call the refresh.

Now that I have this setup with the DevEx grid I'm getting some completely different behaviors than I was with the EnhancedList.  For example, I create a new record and go to input the data into my bound fields.  I select a date from a drop-down and it checks the business rules when I do the selection instead of when I call save.  I'm not sure how this is happening, but it's causing the red error icons to pop up before I actually save.  I can't input everything in before it starts popping error icons. 

Also, If I create a new record and then undo it gives me an error sayig that the current row is out of range.  This is true because for some reason it's hanging on to the new record it creates.  I'm not sure what the difference in the interaction is between the GridControl and the BO vs. the EnhancedList and the BO, but it's very different and I'm not sure where I'm going wrong getting these to work together. 

When I create a new record, it creates a blank row in the grid before I have saved it.  I think this is causing my index out of range problem.  What in the BO is causing this to happen in the grid?  I don't understand how these work together...I thought it would be the same as the EnhancedList since it was inherited.

I have it figure out.  I was Navigating by primary key on a FocusedRowChanged event, but the grid was firing that event when the data source was changing so it was trying to navigate when it shouldn't have been.  I changed the event to a click so it would only be on user interaction.  Works great now.

You could also change the CheckCurrentRowBeforeNavigate property to false so that the business object will not check the business rules on the row before it attempts to navigate the CurrentRowIndex.  The business rules would still get checked before it saves, though.