bug: 3th form of same table doesn't sync right

[Harjo]

In the CRM-demo: goto actions.
first: filter: faxes. ( in the upper header)
then goto the details of the first fax.
Try to print this fax only. this doesn't work. (first it gives a message that there are no messages, en than all the records are shown in print-preview.

I have the same problem in my solution.
I have one table with forms in: record-view, list-view and print-view. If I filter for example 3 out of 10 records than my record-view and my listview are showing: 1 out of 3. but my printview shows still the previous foundcount.
It looks like the 3th form of the same table doesn't sync right with the currentfountcount.

[Jan Blok]

This is indeed a crm solution bug
A foundset is shared across forms based on the same table and as long as:
-useSeparatefoundset property is not used
-you don't do controller.loadRecords(xxxxx) on one of those forms via javascript

the last one is used to jump from actions to actionDetails, so in this senario you have to transfer the current foundset again from actionDetails to printFax with:
forms.printFax.controller.loadRecords(foundset)
just before showPrintPreview call on the printfax form.

[Harjo]

OkM-i, so I have changed the method: printfax (just deleted the "//" before the specefic line)

but it goes wrong when you only have 2 related records.
It's rather complecated but I give it a try!

To reproduce, goto CRM, after that goto Employees,
goto the employDetails of: Jim Smith. Delete all actions of: Jim Smith, except for two faxes. (so you only have two related actions)

Go, in this form, to the details of the first Action
Push the: PrintFax button, after that click the CLOSE button

Now it goes wrong! Servoy is ending now on the other related Action!!
If you push the button: Printfax again, it is not showing the second related Action, but the first again.

This only happens when you have 2 related records. If you make 3 related record (in this case: Actions) this problem does not occur!

[Harjo]

Can anyone re-produce this problem?

[jcompagner]

Yes i found the problem
fixed in then next build after 1.1

[Harjo]

Thanks, do you know when the next build is coming out?
And will it be a RC or R-Release?

[jcompagner]

this week we will try to release a beta of 1.1.1 and then next week the release of 1.1.1.

so it will not take long