Find 1 record, Delete 2???

[BLOMASKY]

This is version 8.8 build 3127. The screen shot shows it all. I have a FIND that returns 1 record, then next line is a DELETE and if there are only 2 records in the BO it deletes them both. If I have more then it usually works OK.

Any suggestions?

Screenshot 2023-07-14 at 8.11.40 PM.png (420.91 KiB) Viewed 9923 times

[Jaymer]

thats because there are 2 in context.
you've done 2 FINDs

do a LOG2 CONTEXT

[BLOMASKY]

I thought it would only delete the LAST find.

Thanks

Bruce

[PointsWell]

I thought it would only delete the LAST find.

Thanks

Bruce

Only if you've:

• Used DELETE ThatPermanentSchedule or
• created a sub process that doesn't feed the PermanentSchedule record to it to do the FIND

OR: Put a failsafe in

Code: Select all

IF SEARCH_COUNT = 1 THEN DELETE PermanentSchedule
ELSE IF SEARCH_COUNT < 1 DISPLAY MESSAGE ASYNC " No records found"
ELSE IF SEARCH_COUNT > 1 REPORT ERROR "Process stopped multiple records found"

Personally I am a fan of many small processes with controlled context and either fresh FIND actions or the use of NP BOs as a carrier to pass the required BO but disguised as a different BO.

Eg

TempPermSch with one attribute psPermanentSchedule that you can then pass to a sub process and interact with without having to remember This or That

[customaware]

Another way of doing it which is great when you have more than one instance.....but more applicable when you have 3 or more....

Create a Non Persistent Business Object that has as many Reference Attributes as you need... For example.... assume you need to bring 4 different instances of a BO into context to do some comparison or whatever.

Create NP_My4BOs with ps_Instance_1, ps_Instance_2, ps_Instance_3 and ps_Instance_4. Injected each of your instances into the Reference Attributes and then you can pass the NP BO between any Processes and it takes all of the instances with it.

[PointsWell]

Another way of doing it which is great when you have more than one instance.....but more applicable when you have 3 or more....

Create a Non Persistent Business Object that has as many Reference Attributes as you need... For example.... assume you need to bring 4 different instances of a BO into context to do some comparison or whatever.

Create NP_My4BOs with ps_Instance_1, ps_Instance_2, ps_Instance_3 and ps_Instance_4. Injected each of your instances into the Reference Attributes and then you can pass the NP BO between any Processes and it takes all of the instances with it.

I've used a similar setup to create quite complex double entry bookkeeping transactions (I.e. transaction plus commission plus tax) using only a few process steps.