Can a Not Persisted BO hold multiple instances?

rbross

I Have been looking through the User guide and cannot find if a Not Persisted BO can hold more than one Instance of the BO (records).

I created forms using the Wizard-Like form entry for a registration process and one the forms needs the option to be able to enter more than one record. The fields are just First Name and Last Name.

If it cannot hold more than one instance would it be best to just repeat those fields in my Not Persisted BO to allow for multiple entries on the form?

Thanks

Roger Ross

Windows 7 Pro AwareIM ver. 6.0 Build 1975

BenHayat

rbross wrote
I Have been looking through the User guide and cannot find if a Not Persisted BO can hold more than one Instance of the BO (records).

I created forms using the Wizard-Like form entry for a registration process and one the forms needs the option to be able to enter more than one record. The fields are just First Name and Last Name.

If it cannot hold more than one instance would it be best to just repeat those fields in my Not Persisted BO to allow for multiple entries on the form?

Thanks

Roger Ross

Windows 7 Pro AwareIM ver. 6.0 Build 1975

Technically it should, I haven't tries it. It's just like having a in-memory Observable Collection that many OO languages support. I plan to use None Persistent BO heavily because of performance and collection is one of them.

Let's hope support would jump in and shed some light and provide more info.
But good question.

customaware

In short guys......

Non Persisted is really for on record at a time.

Reason being....you will not be able to keep more than one record in context.

I am happy to be corrected but....

No matter how many records you try and CREATE, each overwrites the last.

The record will be CREATED in a process and you can very easily lose context....for example...

Create a NP BO called name with attribute Name.
Now create a Query of All Name.

Create a Process that...

CREATE Name WITH Name.Name='Jones'
CREATE Name WITH Name.Name='Smith'

You cannot then COUNT Name
You cannot DISPLAY the Query All Name

Also, any further process that you pass Name to will only have the last created instance in it.

So (again, happy to be proven wrong) from my experimentation, only a single instance of the BO will
be held in context at any one time.

BenHayat

eagles9999 wrote
In short guys......

Mark, when you created the multiple instances, did you have an attribute like ID that takes an INT type and has an auto Increment feature to give the instance a unique value?

hpl123

Try playing around with the context some. I for example think (not tested) this would work (i.e multiple instances in context with non persisted BO):
CREATE Contact WITH Contact.FirstName='c1',Contact.LastName='c1'
CREATE Contact WITH Contact.FirstName='c2',Contact.LastName='c2'
CREATE Contact WITH Contact.FirstName=ThisContact.FirstName,Contact.LastName=ThatContact.LastName