Strange nested procudere behaviour

GertV

I have a prodedure SendNewsletterToMembers as follows:

FIND Newsletters WHERE Newsletters.ID=LoggedInSystemUser.ChosenNewsletter
FIND Emailaddresses WHERE Emailaddresses.Newsletter='Yes' IN BATCHES OF 1
FIND Members WHERE Members IN Emailaddresses.Member
SEND NewsletterOutNotificationMember TO Emailaddresses

When I run this procedure from the Query Newsletters directly it runs fine. However I want to run a procedure SendNewsletters that does the following:

SendNewsletterToMembers
SendNewsletterToFriends

So basically calling the the procedure from another one.

When I run the second scenario the following strange thing happens:

Find Newsletters finds the right Newsletter
Find Emailaddresses finds 346 instances
Find Members finds 1 instance for each Emailaddress
When the first object is processed all goes well.
When the second object is processed it seems it keeps the old value of Members, i.e. the Member it found in step 3 for the first object.
The NewsletterOutNotificationMember contains a HTML message that is filled with a template referring to fields from the Members table. For the first object the template fills well, for the second it returns an error message -Failed to fill document template NewsletterMember with data

Again, on running the procedure directly from the Query it sends out all Newsletters as expected, but when I run the procedure as a nested procedure it gives the above errors.

Is this a bug or am I overlooking something?

himanshu

Hi Gert,

I think your problem and the following issue are same under one head.

tford

I don't really understand all of your logic, but I usually use sub-processes & pass the parameters via process inputs.

For example:

Process1:
FIND Newsletters WHERE Newsletters.ID=LoggedInSystemUser.ChosenNewsletter
FIND Emailaddresses WHERE Emailaddresses.Newsletter='Yes'
Process2

Process2 (process input: Emailaddresses):
FIND Members WHERE Members IN Emailaddresses.Member
SEND NewsletterOutNotificationMember TO Emailaddresses

himanshu

Hi Tom,

How are you doing!

May be something wrong with my side but if you need a bsv to reproduce then i can send it to you..right away..

🙂

Thanks,

tford

Himanshu -- my answer was to GertV.

himanshu

okay,

I assume that there is some relation with all three issues.

As in my test also first record process well but after that it fails.

Thanks Tom,

GertV

Tom,

Thanks for your suggestion, which I tried out. Unfortunately I am getting exactly the same result as with the procedure I used before, i.e. The first newsletter is send out correctly but any other after that fails.

Could it be a bug?

ACDC

I find when I run into problems similar to this, its because the first part of the process is still in context when it should not be.

Try experimenting with some other options similar to Toms suggestion, i.e. chaining to a new process

Also remember to insert the correct input in the process you drop out to, this will ensure the correct context is formed - very often this has been the culprit for me when a chained process doesn't produce the right result.

GertV

Hi ACDC

I meanwhile managed to solve the problem by rewriting the whole procedure (following your and Tom's suggestions) and by calling a process using the USING Newsletters clause.

Also I found out that my AwareIM environment was acting weird. It kept locking my version where it should not. So I reinstalled AwareIM and the procedures are now running fine.

Thanks for your help.