Cannot Save Resources in Project Pro After Upgrade

Question

I have recently migrated a test environment from v2003 to v2007 to v2010 to v2013.  All project plans, resources, custom fields, security, etc. have migrated cleanly and all functionality seems to be intact.
However, when I open any global resource within Microsoft Project Professional 2013 in order to update their information (cost rate tables in my case), the changes will not save.  There are no errors thrown to the client.  The screen "blinks"
and just doesn't finish the save.  The same resource can be updated from PWA with no issues.
Errors I can see:
ULS -
PWA:http://server/pwa, ServiceApp:Project Server, User:i:0#.w|domain\user, PSI: [ProjectServerError] Mismatched Attributes for PSErrorID CustomFieldRequiredValueNotProvided. List of defined attributes: mdpropuid. List of provided values: none., LogLevelManager
Warning-ulsID:0x62307279 has no entities explicitly specified.
Fiddler -
<s:Envelope xmlns:s="<faultcode>s:server</faultcode><faultstring">http://schemas.xmlsoap.org/soap/envelope/"><s:Body><s:Fault><faultcode>s:server</faultcode><faultstring
xml:lang="en-US">ProjectServerError(s) LastError=CustomFieldRequiredValueNotProvided Instructions: Pass this into PSClientError constructor to access all error information</faultstring><detail><ServerExecutionFault xmlns="http://Microsoft.Office.Project.Interfaces/"
xmlns:i="<Actor">http://www.w3.org/2001/XMLSchema-instance"><Actor i:nil="true"/><LastError>11713</LastError><Message/><Source/><StackTrace/><TargetSite
i:nil="true"/><ExceptionDetails><errinfo xmlns=""><dataset name="ResourceDataSet"><table name="ResourceCustomFields"><row CUSTOM_FIELD_UID="e14f26a8-cde9-e411-8276-d20f3ee8a73b"><error
id="11704" name="CustomFieldInvalidTypeColumnFilledIn" uid="eb2ffca7-cde9-e411-bad3-005056822892"/><error id="11713" name="CustomFieldRequiredValueNotProvided" uid="ec2ffca7-cde9-e411-bad3-005056822892"/></row></table></dataset></errinfo></ExceptionDetails></ServerExecutionFault></detail></s:Fault></s:Body></s:Envelope>
During the migration, there are 7 project and resource fields that are tagged as "required".  If I reset them to not be required within v2013, the problem persists.  However, if I delete those fields completely, this problem goes away. 
Since I have 4000 resources (and 2 of the fields are Cost Center and RBS...), I am desperate for an alternative solution!
Thanks for any thoughts.
Jason

Answer 1

I can definitely save resources in the 2010 instance (even though the SPs and CUs have not been applied there).  The 2013 instance is only running SP1.  CUs have not yet been applied to catchup the environment.  While that is planned to occur
in the next couple weeks, do you think that is an activity we should prioritize as it could potentially address this issue?
Thanks for all your suggestions.
Jason