In my script I need to be able to select all the child records from a set of parents, so I'm using GTRR and the option to 'Match all records in the current found set'.

 

The parent set actually contains some records that have no children, but nonetheless the other parents DO have matching children and script step produces error 101 (Record is missing) - but it actually completes the script step and shows the found records in the layout as required.

Further investigation reveals that error 101 is produced if the current parent record has no children, but there is no error when the current parent HAS got children.

So, the conundrum is how do I determine if the error 101 is actually because there are NO children at all for all the parents, or there are some children for all the parents.

 

As a workaround I can test the current layout name after the GTRR which proves that the GTRR executed fully and ignore the error code.

 

Should there really be an error 101 for this action?

 

I've noticed this as well, and use the same test for layout name being different after the GTRR step rather than testing Get ( LastError ).

 

It's been a while now, and I forget how I came to this conclusion, but I thought the cause was slightly different than you described. I though it was due to an invalid match, like a multi-key field with 5 keys where 4 related records exist and the 5th does not.  I suppose this is just different than what you discovered was the cause; they probably both throw error 101.

 

Should it cause an error?  I think that's debatable, but the bottom line is that it does and that's probably not going to change. I've stopped testing for error after GTRR no matter how I use it. I use other methods to determine it's success/failure like the test for layout name, or counting related records before the GTRR step, if it only involves a single parent.

Should there really be an error 101 for this action?

 

yes but that is not what you should test for with GTRR if you want to know if there are NO related records.  Test for 401 instead.  101 tells you that the first record in the set you are attempting to match does not have a child. It continues to the related table because there are other parents with children.

 

It seems a bit strange but it is actually logical.  You may want to know the difference at some time (although I have never needed to use it that way).