Re-Order Records

customaware

Hmmm.... I thought I understood how to do this but obviously not.

I have a BO with 7 records in it. It contains an Attribute called RecordOrder. And the records are number sequentially 1 thru 7.

I want the user to be able to delete any record and have a process renumber them. For example, if the user deletes record number 4 then
the process renumbers all the records from1 thru 6.

For some reason I had in my mind that SEARCH_COUNT counts down when used in a Rule following a FIND but that does not seem to work.

Any ideas would be great.

BenHayat

eagles9999 wrote
Hmmm.... I thought I understood how to do this but obviously not.

I have a BO with 7 records in it. It contains an Attribute called RecordOrder. And the records are number sequentially 1 thru 7.

I want the user to be able to delete any record and have a process renumber them. For example, if the user deletes record number 4 then
the process renumbers all the records from1 thru 6.

For some reason I had in my mind that SEARCH_COUNT counts down when used in a Rule following a FIND but that does not seem to work.

Any ideas would be great.

I'm struggling with the same thing to do a simple re-sequencing if user adds or delete a record to the top or middle or end. I have done this in other systems and languages, but Aware seems to fail, because it either duplicates or skips a sequence #.
I'm trying to come up with a new strategy, but something works strangely in Aware.

customaware

Hi Ben,

I am very close but for some reason Aware does not process the records in the same order as they are returned from the FIND

For example..... in a BO you have an RecordOrder attribute and a Price attribute and you ALWAYS want the records to have the RecordOrder and the Price order the same.

So you have 10 records that are all ordered correctly.

I have a reorder process which is called when a record is deleted....

SystemSettings.TempMyBOOrder = COUNT MyBO
FIND ALL MyBo ORDER BY MyBo.Price DESC

SEARCH_COUNT>0
CallSubProcess

Parameter MyBO

MyBO.RecordOrder = SystemSettings.TempMyBOOrder
INCREASE SystemSettings.TempMyBOOrder BY -1

The renumbering all works BUT not in Price Order.

Cannot work out why and is driving me nuts.

tford

Have you considered IN BATCHES OF 1?

customaware

Here is a demo…..

The 6 records are in Check Data Order and the Record Order is numbered accordingly.

Add a New Record with a Check Data Order of say, 280

Notice that the Record Order is sequential BUT the Check Data Order is incorrect. Even though the FIND in the process
To Reorder the records had them ORDER BY Check Data Order.

Ok…now use the arrow up / down buttons to manually reorder the records so that Check Data Order is in the right order.

The order should now be 110, 190, 215, 280, 345, 476, 550 and numbered 1 thru 7

Now delete record 4 that has a value of 280.

Ideally the records should be order by value 110, 190, 215, 345, 476, 550 and numbered 1 thru 6
However, they are ordered 550,190,215,345,476 and 110

But I can find no rhyme or reason to the logic of how that works and can find not solution to have the process
Renumber the records correctly.

ReOrder.zip

35.81kB

tford

Mark,

Two changes will solve your issue:

1) make the first two steps in the process unique rules in the process instead of bundling them together.

2) use IN BATCHES OF

customaware

Thanx Tom.

Did you actually try that.

I have the IN BATCHES OF 1 in there previously and it went into an endless loop when I try and deleted a record.

Have now changed to EXACTLY as you described and it still goes into an endless loop when I delete the record.

I suspect it is because the Process is being called from a Delete Rule but not sure.

But if yours works then I am stumped.

Off to bed... A task for tomorrow.

tford

Mark,

I had not tested the delete process. In the BSV below, I changed the delete operation you had on the query to run a process instead. The process now first deletes the selected instance of Reorder, then runs the process to re-order records. I eliminated any process running in the "when object if deleted" section of the Config Tool.

reorder_revised.zip

34.84kB

customaware

Perfect Tom.

That now works precisely as I had hoped.

However, it does pose a couple of questions in my mind which are at the crux of really understanding Aware IM processes.

Firstly, In a previous post above you talked about separating some steps in a Process to be in two unique Rules. Why and what is the logic that makes that better?
Secondly, while I am delighted that this works by calling the process as an operation rather than from a Delete Rule, I really cannot understand why the later does not work.

I think this is an area that many struggle with and it would be great if we were somehow able to assemble a Dos and Don'ts for Processes.

When to separate into different Rules
When to move Actions into a Sub Process
Things to remember when doing CREATEs
and on it goes....

Anyway, Thanx again Tom for you expert assistance and Ben, download Tom's Re-ReOrder Revisited bsv and try it. I suspect that is exactly what you are looking for.