There are changes related to the following primary key that can cause data loss in the new table. The changes cannot be handled ...

There are changes related to the following primary key that can cause data loss in the new table. The changes cannot be handled because the TableUpgradeMode of the TableSyncSetup type function for the changed table is set to Copy, which does not copy data to the new table. To fix this issue, you must change the TableUpgradeMode option to Move, then add C/AL code to an Upgrade type function to handle new table data.
Original table: {0} '{1}'
Field Id: {2}
Field Name: '{3}'

The {0} database on the {1} server must be converted by {2} before you can use it with this version of Microsoft Dynamics ... The {0} FlowField in the {1} table is not a Boolean field. If a FlowField CalcFormula starts with 'Exist(.', then the FlowField ... The {0} FlowField in the {1} table is not an Integer field. If a FlowField CalcFormula starts with 'Count(.', then the FlowField ... The {0} record with the same EntryId has already been processed. It will not be possible to send post-update for the {1} ... There are changes related to the following primary key that can cause data loss in the new table. The changes cannot be handled ... There are entities which depend on this entity. If you delete it, the relation to its dependencies will be removed.\Do you ... There are errors in the text conversion because of an incorrect internal buffer length in relation to text no. %1-%2. Internal ... There are errors in the text conversion because of invalid .stx syntax. The error occurred in the file %11 on line %12 in ... There are errors in the text conversion because text no. %1-%2 is too long for the internal buffer. Internal error: 47-%0 ...