You’re offline. This is a read only version of the page.
3,905
Hey Guys,
there seems to some internal things going wrong within Ax2012. If you rename an ExtendedDataType (here it is a string) and have already used this within ExtendeDataType property of a table field, something is going wrong, or better said: does nor work as in Ax2009, where this worked like a charme.
Ok:
Let's say we have (working in the usr layer) a string ExtendedDataType MyEdt100 / Length 100
Addtional we have a Table with two fields / Field1 and Field2, Field2 is assigned this EDT.
Now, due to a typo or something other, we must rename our EDT lets say from MyEDT100 to RenEDT100.
First of all, you will notify a warning on synchronisation of yout table.
If you look at the table field properties, you will see your old EDTName. Just for Information, I additionally changed the Length on RenEDT100 to 90 before making the hardcopies. This shows that the field knows its real assigment (RenEDT100/FieldLen 90)
If you now select the ExtendedDataTypeProperty (click in) you surprisingly see the following
If you leave this, the MyEDT100 is shown again:
So it seems that the Field internally has both properties, the info: I really was renamed to RenEDT100 and somewhere the string 'MyEDT100' which was somewhere assigned?
Problems arise if you export your project:
Within the XPO the wrong Name is exported and there is no other information related to RenEDT100 in it.
So lets delete your project and reimport (or import the xpo on another instance)
A warning appears. Minor Changes.
and after Import the Field das not have any EDT assigned to it.
This did not happen in Ax2009.
So keep in mind this if you plan to rename EDT Names for some reasons. Think you have to go to each field and reassign the renamed edt.
Did anyone has a solution which allows updating all the references in a secure way??
Do not know if this is a 'by design feature' but you should keep an eye on this.
regards
Douglas
*This post is locked for comments
I have the same question (0)
Hi,
some additional information.
if you go to the table after renaming and do a restore, even the length is set back to 10 and the complete assignment to the edt is lost.
And morever. This happens if you, after renaming the EDT restart the connected AOS. Maybe two days later.
Your field is now ExtendedProperty 'No', Length 10.
If you don't read exactly the warnings on synchronisation, because you are expecting warnings due to other developments. You will cut your data.
I would say: This can't be a feature, is it?
regards
Douglas
Share
Report
All responses (
Answers (
