What am I doing wrong here? I am using 8.5.0.1815 for this example.

Create a simple QBM in DE8.5 with two fields.

Then remove one field via Document >> Query by Model screen.

When you hit the OK button, it does not remove the field from QBM.

Even right click in the middle of the body, then layout, then check mark for 'Do you want to automatically recreate the layout, then click OK.
Still nothing happens. As you will see on the attached video, I am trying to remove one field 'Address'.

This was changed in 8.2 THE QBM model was changed so the Layout has the priority in QBM.

Simply remove the field in the layout.

Actually, it is NOT simple as that. May be I am doing something wrong here.

When you have a grouping in QBM. Then later, you want to add another grouping. QBM does not allow you to recreate the layout.
It seems like you have to start the QBM from scratch by selecting all the field, summary, grouping....etc. ??

Hi again Arul.

As they said in the British Navy.... "The lesser of two weevils.."

I must of course admit that it was not very wise to even try to fix QBM and DQL, but we did an attempt in 7.2 (had to revert) and we did an attempt again in 8.2.

The only thing we learn each time is that it is flawed on so many levels that you can't really fix it and hope that it would work.

There is two contradictory problems.

1. It doesn't work.
2. It is being used.

So if you fix it, what worked before change and you get complaints because what used to work doesn't "work" anymore.

The main problem with QBM and DQL has been that there is a Mismatch between Layout and the Data Model it is built on. The worst is DQL but almost as bad in QBM.

To add insult to injury, the automatically generated layout is "hopeless". 

If you want to use QBM or DQL to make any sensible printer you need to do it manually. The automatic layout is only helpful for developers testing, for any other purpose you really need to do it yourself.

Why one think that automatic layouting is more helpful on reports than it is on forms, beat me but we might put it down to traditions and it is quite useful when you do listings.

So our goal in 8.2 was to make sure that the LAYOUT took the ownership of the QBM rather than the model.

So when you insert a field (virtual for instance that is not in the model) it will stay there, and when you use the model to sort on a field that is not visual in the print you are NOT forced to ruin your layout.

Pre 8.2 you really had to insert a new subform or a new group (which is a subform as it turns out) in the model and have DataEase "forcefully" insert it in your layout, where you could then move it about and reformat it and then you could delete all the fields that no longer worked and re-insert them etc.

To be honest, to make any kind of print with QBM and DQL is/was a horribly tedious affair, and this is what we attempted to improve.

Now the Layout is the "boss" after the first auto generated layout, and yes it might be a nice thing if  you could start over but to be honest that is only important when you are playing around. If you are trying to build a proper print it is more important that your work is not ruined by DataEase than the other work around.