Getting The field with Id 0 does not exist in table message

If you get this message: "The field with Id 0 does not exist in table" you might find yourself in one of the following situations:

Getting Cannot insert the value NULL into column message

If you are getting "SQL error description: [Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot insert the value NULL into column 'xyz', table 'tempdb.dbo.t_longId'; column does not allow nulls. INSERT fails." you can look to see if you are in the following scenario and understand what you should change.

Getting You are not authorized to access table message

If you are getting this message "You are not authorized to access table ‘Table label’ (TableName). Contact your system administrator." when trying to use the Table browser and you are a SysAdmin in AX, which is rather interesting, this is one possible thing you are overlooking:

Getting Failed to create a session message at Synchronize (II)

Blogged about this issue last month, after couple of years of trying to find a fix that will always work and get us to the desired result of not seeing the error. Turns out, my post at http://axfaq.blogspot.ro/2015/07/getting-failed-to-create-session.html did not necessarily fixed the problem, as I discovered: several days after blogging I found myself in the same situation and I wasn't able to pass the issue.

Use data db with a new model db

I was trying to find a simple and efficient way to actually get one instance data database to work together with anther instance's model database. Of course, one thing to remember, the models installed on the two instances were 99% identical (I'm saying 99% because one might have received several new object with the higher models imported).

Getting Failed to create a session message at Synchronize

Long has been since I started to see this error message when doing a Full Data Dictionary synchronize: "Failed to create a session; confirm that the user has the proper privileges to log on to Microsoft Dynamics.". I tried the solution of setting the SID of my user for the rest of the Admin records created in other partitions, however, this didn't provide the solution all the times.

TempDB error when calling linkPhysicalTableInstance

I got this when using a TempDB table in a form as a datasource: "Cannot execute the required database operation.The method is only applicable to TempDB table variables that are not linked to existing physical table instance.".