If you add a field to a table in the USR layer, using a an EDT that was defined in the USR layer, the filed will exist on the table in the USR layer, it gets a fieldId in the range of USR layer ID’s, if you come back later and change the EDT on that field to an EDT defined in that VAR layer, the field on the table will STILL exist in the USR layer and with the same FieldID it had before, EDT used will not affect the layer of a field.  If you want this field in another layer you will have to delete the field from the table, and re-add it in the appropriate layer.  Keep in mind Axapta makes use of fieldID’s in classes, forms and report definitions even though it’s not readably visible , and doing a change like this will most likely mean touching every other object in Axapta that is currently using that field, also if the field contains data you will have to come up with a plan to preserve it.  It may be wiser to create a new field in the desired layer, create a job to copy data from the old to the new, and then edit each of the AOT objects that make use of the old field to point at the new; you can then safely delete the old field.

 

-Preston

 


From: Danny Gaethofs [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 25, 2005 6:32 AM
To: Axapta-Knowledge-Village@yahoogroups.com
Subject: [Axapta-Knowledge-Village] Changing ID's Extended Data Types

 


Dear all,

I have a situation where extended data types are created in the user
layer and need to transferred to the var layer.

I have done some tests and those show a change will not influence the
data in the database.

However just to be sure, will a change of id have an influence on
axapta. I am replacing the user defined extended data type with one
defined in the var layer.

regards,
Danny





Sharing the knowledge on Axapta.




Sharing the knowledge on Axapta.



Yahoo! Groups Links

Reply via email to