No, what you described is the standard behavior. Wonder (ERXEC) provides a
way to include the unsaved changes if you desire, but this is not the
default/standard.
On Mon, Aug 12, 2013 at 2:31 PM, Lars Sonchocky-Helldorf <
lars.sonchocky-helld...@xyrality.com> wrote:
> So you're suggesting that
I haven't check the "normal" EC management, but I'm pretty confident that if
it's not the default behavior in Wonder it's because it could be "unsafe".
Xavier
On 12 août 2013, at 21:31, Lars Sonchocky-Helldorf
wrote:
> So you're suggesting that the behavior we are seeing here is specific to
So you're suggesting that the behavior we are seeing here is specific to ERXECs
and not to "normal" ECs?
cheers,
Lars
Am 12.08.2013 um 21:26 schrieb Dev WO :
> Hi Lars,
>
> You could overwrite (or create another) method "fetchAllPaymentCustomers" to
> apply:
> setIncludeEditingContex
Hi Lars,
You could overwrite (or create another) method "fetchAllPaymentCustomers" to
apply:
setIncludeEditingContextChanges(true)
I recall a discussion about this stating it was "on purpose" that Wonder
doesn't do it by default. So you have to manually deal with it that way you
actually know
You can use an ERXFetchSpec to include objects that only exist in the EC. I
believe there's a bug in that which causes duplicate EOs to show up when using
nested ECs though.
On Aug 12, 2013, at 10:37 AM, Lars Sonchocky-Helldorf wrote:
> Hi list,
>
> we are creating a new EO and insert it into
Hi list,
we are creating a new EO and insert it into an ERXEC like this:
public static PaymentCustomer createPaymentCustomer(EOEditingContext
editingContext, Integer creditScore, String fullQualifiedClassName, Integer
ingameId)
{
PaymentCustomer eo = (PaymentCustomer)
EOUtilities.crea
