Problem with child reference default vs process

Rennur

I'm stuck & can't figure this one out.

Order BO has an OrderPayment child BO (1:1 relationship)

Works:
If I use a default 'Add New' implementation, the OrderPayment is created displayed on the Order [Table of Items reference].

In the database:

On the Order form:

Problem:
If I use a process 'Start Process' with Order as process input, the OrderPayment is created but it does not show up on the Order [Table of Items reference]

In the database:

On the Order form:

Relationship to OrderPayment ref :

Relationship to Order parent :

Any ideas?

Cheers

aware_support

You shouldn't be concerned about values in the internal tables and columns that Aware IM manages behind the scenes

Rennur

You shouldn't be concerned about values in the internal tables and columns that Aware IM manages behind the scenes

Thanks support but I wasn't concerned about that at all.
The images posted are merely to point out a difference in the created objects stored in the database for each of the methods used.

My concern is that when I create a child object using a process it does not show in the parent object's form.

Can you help me with that please?

aware_support

Are you sure this is not just a refresh problem?

Rennur

Troubleshoot so far:

1) I've got the process in the auto-refresh & I can see the BO getting refreshed after the process is finished.

2) I've also saved the Order BO, closed it and re-opened it and it is not there.

3) No query filter.

4) Process:

a. Process input = Orders
b. Rule:

If 
Orders.Order_Payment_EFT IS UNDEFINED 
Then 
ENTER NEW Order_Payment WITH Order_Payment.Orders=Orders,Order_Payment.Type='EFT' USING ENTRY 
Else If 
Orders.Order_Payment_EFT IS DEFINED 
Then 
REPORT ERROR'Payment already exists'

Rennur

SOLVED

Seems that the INSERT statement is required after the ENTER NEW.
This is possibly because there are a number of matching attributes (OrderPayment_CC, OrderPayment_EFT etc.) owned by the Orders BO.

Cheers