By Tony Charpentier - 11/26/2012
Hi,
i try to add a new field in Table and i have this error message,
With the another table all is ok but just this table have the problem !
it's the field tmu_icone witch we try to add in the table. and we have test with other name
like "test" , "aaaa". No way it's doesn't work
if you have an idea , it' ll be appreciate ??
We have just install the last version 1.7.6.0
thanks
tony
|
By Michel Levy - 11/26/2012
Hello Tony,
- on a new DDT project, I raise no error with your definiton
- on your DDT project (this one you gave me during the training), I raise an error which is not related to this column. The strange issue is that the pkg file is created, and the definition of the column id_icone is well defined in the fields.xml inside the pkg.
Would you please send me (e-mail) the pkg file and a backup of your Strataframe database please?
|
By Ivan George Borges - 11/27/2012
Hi Tony.
Also, have you checked your Project's "Object Name History" node to see if you are deleting the table or something like it?
|
By Trent L. Taylor - 11/27/2012
Tony, are you getting this error when you click the "save" when modifying the table? Let me know when you get this error message. Thanks.
|
By Tony Charpentier - 11/27/2012
Trent : i have this error when i deploy.
Ivan : i dont delete the table, i just add a field.
If i delete the last field create, i can deploy without problem.
thanks
|
By Trent L. Taylor - 11/27/2012
Yeah, there is something in your environment. Can you do like Michel asked? I would like to look at the DDT package and possibly the StrataFrame database like Michel mentioned.
|
By Olivier - 11/27/2012
Hello trent,
Tony work with me, and he send the package and save database to michel.
We wait the analyse's michel.
thanks
Olivier
|
By Trent L. Taylor - 11/27/2012
Okay, sounds good Oliver. I am sure that Michel will get you going down the right path. 
|
By Michel Levy - 11/30/2012
Fixed 
1st error: They didn't update the good SF database (another one on their LAN). Let's update the good one, and no more error when creating package, but still when deploying.
2nd error: the infamous #1026, because data to deploy refers to a modified table in structure deployment.
So we delete the data deployment in the profile to package, and all is ok now.
Maybe a warning in DDT would be fine, if one ask for deploy in the same package data and structure modifications for the same table.
|
By Ivan George Borges - 11/30/2012
Aha! It looks like I was on the right track.
By the way, every time I change the structure to a table that has a deployment package, I simply run the DDT deployment twice. The first time I will get the error while creating the package, but then it updates the structure on the database and for the second time everything goes fine.
|
By Trent L. Taylor - 11/30/2012
Thanks for your help, guys!
|
By Olivier - 11/30/2012
hello Ivan,
We have deploy several times and the error stayed always.
If Michel, we had not say , i know this error, you must to remove your deploy meta data,
the error was always here.
May be the DDT 2.0 ll catch this error to inform the user to destroy the data deployement.
And more if we can store in DDT our meta data stand alone without sql server, it'll be great.
thanks
Olivier,
|