Adding columns to BO - what on earth just happened

CalD

Hi Everyone,

Here I was adding a bunch of columns to an existing BO. Added them to the form of its parent as I wanted to etc, all appeared fine. Went to switch to testing mode and got a message in the syntax checker that there is an internal problem and I need to go to the tree and press ctrl+i to rectify it, so I do this. All good... now I go to switch to Testing mode and I get message about not being able to drop a column in the table because it doesn't exist. Look in SQL Manager (using MS SQL) sure enough it doesn't exist...
On closer inspection more columns don't exist, and its not just the new ones I added some are columns that have been there since the inception of the BO...

How do I get this back - fortunately its test environment but I would still like the table with data back...?
Also does this sort of thing ever happen when people make new versions live?

Bit scary

Cheers
Callum

tford

Backups are crucial.

I've never had this happen, but I have published the wrong BSV to a production server which caused a ton of table changes that I obviously did not intend to make. Thankfully I quickly realized my mistake and was able to restore all of the tables of that BSV from a backup done just before publishing the BSV.

CalD

Completely agree about the backups being important... in Dev though i wasn't expecting such a problem and my backup in dev is too old... all I have been able to do it get it operational again is to tell it to not use previous testing data and start fresh... I couldn't see a way whereby I could remove the 1 table from SQL and have aware recreate it or anything. I tried adding the fields aware said were missing 1 by 1 and attending to each problem aware was throwing at me, but eventually it looked like aware was trying to rename and convert fields etc and it was all well confused.

An option to just drop the whole table from aware and recreate it empty would have been handy!