yes, I have encountered this. it is a direct result of the location now supporting default dimensions. The results can vary depending on your dimension setup and the order in which fields are validated. I suspect that Microsoft didn’t fully test the impact of this change.
I encountered this is a page used for a web service. My solution was to change the order of the fields to get the desired dimension behavior. The use of dimension priorities may also help in some situations.
Note: When a field supplies any default dimensions, it doesn’t just update the dimensions that are on the related record. Rather it recalculates all of the dimensions.