How to fix - "Illegal data conversion from original field" errors

-
At one time or another, most of you must have come across one or both of these errors,

Case 1:
Illegal data conversion from original field Table1.FieldX to Table2.FieldY: Unable to convert data types to anything but

character field type (0 to 4).

Synchronize database Cannot execute the required database operation.The SQL database has issued an error.

Case 2:
Illegal data conversion from original field Table1.FieldX to Table1.FieldY: Unable to convert data types to anything but

character field type (0 to 4).

Synchronize database Cannot execute the required database operation. The SQL database has issued an error.

The difference between these are that in the first case, the tables as well as the fields are different whereas in the second case the tables are same but fields are different.
Now, there are two scenarios when you may encounter the above error.


  1. While upgrading from one version of Dynamics AX to another version

  2. While importing a project or a stand alone xpo


These errors state that currently there is an already existing object in your system which has the same ID as the object that you are trying to upgrade or import.

So how do we fix these issues?

The fix is different depending on the reason why you are seeing these errors.

If you are performing an upgrade and hit this error, then you will carefully need to consider if it is actually possible

and not a rogue scenario.

To fix this you will have to change the ID of the offending object. The object can either be a table or a field.

While importing, the system checks the SQLDictionary system table to see if an object with the ID as what we are importing

exists in our system? If yes, it throws this errors.

To change the ID of the objects, we can use two methods on the ReleaseUpdateDB class, - changeTableId & changeFieldId

Both these methods are static.

Examples of their usage are,


// Parameters are tableID, Old FieldID, new FieldID, tableName, FieldName
ReleaseUpdateDB::changeFieldId(100,50001, 50002, "Table1", "FieldX");


// Parameters are old tableID, new tableID, tableName
ReleaseUpdateDB::changeTableId( 50001, 50002, "Table1");


The other case when you will see these errors is when you are importing some xpos. The reason why this could happen is that

you may have deleted the AOD file for a layer, then you try to import an xpo. In this case, your database still holds the

schema for tables from the AOD you removed. These were not cleaned up. So you may get an ID conflict error. In this case,

the solution is to go to your database and simply drop the offending table because we dont need it. No need to rename the

table or field here.

Hope this clarifies and helps understand these errors.

Comments

Post a Comment

Popular posts from this blog

How to add empty ranges in query

-
In Dynamics AX programming, a common mistake I have seen when it comes to query ranges is passing an empty string value to the range. The developer here is expecting it to show all the records where the range field is empty. Instead, what we get is all records without the range being applied. As baffling as it may seems, it is easily explainable. The query engine in Dynamics AX, will not add a range if you don’t specify a value or if you specify an empty string because an empty string is treated as no value. So the following code will result in this SQL statement, query = new Query(); qbds = query.addDataSource(tableNum(ProjTable)); qbr = qbds.addRange(fieldNum(ProjTable, Name)); qbr.value(''); Select first fast * from ProjTable; But what was expected was something like, Select first fast * from ProjTable where Name == ''; So to work around this issue, use the SysQuery::valueEmptyString() static method which parses the empty strings correctly so that it
Read more

Get selected records in Dynamics AX 2012

-
Image
In my earlier post, we discussed how we can retrieve all selected records on a list page. You can read that post here . Retrieving all selected records from a caller form is very easy. The code for this can be found in a number of places in standard Dynamics AX codebase. The general approach is to use the dataSource.getFirst(1) statement to get the first selected record and loop through the remaining using dataSource.getNext() . In Dynamics AX 2009, a new class was introduced for this purpose. This was the MultiSelectionHelper class. In Dynamics AX 2012, another new class has been introduced to retrieve the selected records. This is the MultiSelectionContext class. The MultiSelectionHelper class is an application class. It presents two constrcutors. The standard constructor method just creates a new instance of the MultiSelectionHelper class. When this construct is used, you will have to explicitly set the dataSource to be used for fethcing selected records. This can be done
Read more

The field with ID '0' does not exist in table - Cause and resolution.

-
Image
Hello readers, In Dynamics AX coding, you should have come across this error sometime - The field with ID '0' does not exist in table 'SomeTable' So what causes this error and what is the possible resolution to it? Well, the most likely cause for this error is a missing mapping in a table map. Let us look at an example. I've a simple Map named CustVendAccount with one Account field. I've created two mappings - one with CustTable's AccountNum field and for the otehr mapping, I just specify VendTable but no field. This is how my map looks like, Now, I've a simple job which just passes either CustTable or VendTable as an argument and then we print the Account field in the map. static void CustVendAccountMap(Args _args) { CustTable custTable; VendTable vendTable; void readMap(CustVendAccount _custVendAccount) { info(strFmt("Value from table %1 is %2",tableId2name(_custVendAccount.TableId), _custV
Read more