I have a loop searching a members file for invoices due and for each record found it reads a subscription record to find the fee.
There was a record with incorrect data on the members file such that when reading the subscription file there was no match.
In such instances I display a warning message (so the data can be corrected) and allow processing to continue so that other valid records are processed.
The form correctly entered the 'Not found' process on the faulty record and no 'invoice due' record was produced. However, on subsequent records both the 'found' and 'Not found' paths were executed and invoice due records correctly created.
On correcting the data all records were correctly processed and 'invoice due' records produced and no 'Not found' processing occured.
I have simplified the experience down to 3 records where the first has the faulty data. I inserted a message in the 'Not found' path to say the path is entered and the name of the member involved. I also inserted a message in the 'Found' path again with the member name.
I have screenshots of the two tests of before and after data correction and also a screenshot of the loop event. The screenshots show that both the 'found' and the 'not found messages are produced for the two records that are successfully processed in the example where the first record triggers the 'Not found' route. When the data is corrected all three records are correctly produced, with the 'Found' messages but not the 'Not Found' message.
So it appears that once the 'Not found' route is triggered on a read then the processing within the 'Not found' path is entered as well as the processing within the 'Found' path.
Is this a fault or is there some error clearing command I am missing?
Unfortunately, for some reason, the forum is not letting me upload the png files - 'Error saving the attachment file'.
Wallyhowe
There was a record with incorrect data on the members file such that when reading the subscription file there was no match.
In such instances I display a warning message (so the data can be corrected) and allow processing to continue so that other valid records are processed.
The form correctly entered the 'Not found' process on the faulty record and no 'invoice due' record was produced. However, on subsequent records both the 'found' and 'Not found' paths were executed and invoice due records correctly created.
On correcting the data all records were correctly processed and 'invoice due' records produced and no 'Not found' processing occured.
I have simplified the experience down to 3 records where the first has the faulty data. I inserted a message in the 'Not found' path to say the path is entered and the name of the member involved. I also inserted a message in the 'Found' path again with the member name.
I have screenshots of the two tests of before and after data correction and also a screenshot of the loop event. The screenshots show that both the 'found' and the 'not found messages are produced for the two records that are successfully processed in the example where the first record triggers the 'Not found' route. When the data is corrected all three records are correctly produced, with the 'Found' messages but not the 'Not Found' message.
So it appears that once the 'Not found' route is triggered on a read then the processing within the 'Not found' path is entered as well as the processing within the 'Found' path.
Is this a fault or is there some error clearing command I am missing?
Unfortunately, for some reason, the forum is not letting me upload the png files - 'Error saving the attachment file'.
Wallyhowe