Report Builder changes not always saved

[tschutter]

I am using nubuilder-v2.7.4.11-12.10.24-Build529 on Ubuntu 12.10 browsing with Chromium 22.0.1229.94.

1) On Add Activity -> Report, click on the Report Builder button
2) Make changes
3) Click on the Copy Changes button
4) Click OK to dismiss the "Copied Successfully to Activity Table" message
5) Do not click on the Save button
6) Immediately click on the Report Builder button
7) Recent changes are lost

If you click on the Save button at step 5, then the changes *are* saved. The problem is if you immediately return to the Report Builder page.

On a side note, the Copy Changes button would make more sense if it was labeled Save Changes or just Save. It took me awhile to figure out that the Copy Changes button is what I wanted.

[admin]

tschutter,

Copy changes copies changes back to to Activity record. Nothing is saved until the Activity is saved.

Steven

[tschutter]

But the Report Builder is not using the in-memory Activity record. It is refetching it from the database.

Read the original post again. Most users would expect that if you click on the Copy Changes button and then immediately on the Report Builder button that you would not lose your changes.

[admin]

But the Report Builder is not using the in-memory Activity record. It is refetching it from the database.

You are wrong.

[tschutter]

I believe there is some mis-communication here.

On the Report editing page, I click on the "Report Builder" button to bring up the page to edit the report layout.
I make a small change.
I click on the "Copy Changes" button which copies changes back to to Activity record and returns me to the Report editing page.
I click on the "Report Builder" button. The small change that I had just made is gone.

So you said that the Copy Changes button copies the changes back to the Activity record. But evidence shows that when the Report Builder does not load the layout from the Activity record. Yes, I am confused.

[admin]

what evidence?

[zazzium]

tschutter,
i'm confused about your dispute, after a developer has explained how to avoid losing your report design.

[admin]

.