Upgrading to D365FO v10, database sync error 'Failed to create an instance of table, got Common instead.'

I work for an ISV that has clients upgrading to D365FO v10, in some (but not all) instances the client is getting an error while performing the following steps:

1. Install custom project in a tier 1 dev box. The process for that one was:
   1. Delete the existing custom packages.

                                                               i.      A delete via source control of the existing packages.

                                                             ii.      A cleanup delete via windows explorer to ensure everything is cleaned out.

1. 1. Install the new custom package using axupdateinstaller.
   2. Project builds and and the db syncs successfully in this environment.
   3. Then, add packages to source control.

                   i.      Client says they checked in the entire content of each of the packages under packageslocal.

1. The environments at issue (there are two so far.)
   1. We had those environments get latest from source control which would get the delete and then the add of the packages/models.
   2. This is where we wind up with the database sync issue.

The error the client is getting for some (but not all) of the custom SQL objects is:

Exception: Microsoft.Dynamics.Ax.Xpp.ErrorException: Failed to create an instance of table 'CustomSQLObject', got 'Common' instead. Please make sure it has been built.

This would appear to me to be a build server/source control issue, but I would like to confirm that with the community to get a solid answer I can go back with.

As I am by no means an expert in this area, any and all help is appreciated.