Provide ability to modify the Business Object Definition without losing existing mappings

[#1]

It appears that if you currently alter the definition of a business object anything currently mapped to that business object needs some attention. The simplest scenario of adding a new column to a query BO can result in the existing column mappings being lost. For the part of the BO interface that doesn't change surely this could be maintained.

[#2]

I find that this is fixed. IIRC it was fixed in 9.0.3. It certainly is not an issue in 9.1.0 AFAIK. In what version do you find this an issue?

[#3]

I use 9.1 and this issue appears sometimes.

[#4]

Yes, I had this recently in 9.0.3.3 whilst adding a column to a query definition - you lose the column bindings on a grid and have to reset each column.

[#5]

I have just tried this in Build 9.1.0.1872, which is (I think) 9.1.0, and it worked fine.

If you make a mistake and the SQL fails, you will then lose all references. I have learned the habit of saving before editing Business Objects just in case I stuff them up. If you just add a field or fields correctly (and using the SQL builder will ensure you do get it right), there should be no problem.

[#6]

I have seen this in 9.1+ versions. This could be manually changing a query (not using the builder but no mistakes in the query), and I think changing the script supporting a scripted BO. Perhaps I should use the builder more often