Installments field showing wrong number

[GoogleCodeExporter]

What steps will reproduce the problem?
1. We created 7 monthly recurring donations, the forecast month is 24. So each 
recurring donation generates 24 opportunity lines, and the Installments shows 
24.
2. The next day we found the nightly scheduled job created one extra line for 
each recurring donation and now the number of lines is 25, but the Installments 
field still shows 24.
3. However, the Installment field shows 175 in the last recurring donation, and 
the field was last modified by the nightly scheduled job

What is the expected output? What do you see instead?
We expect the Installment field to show exactly the number of opportunities 
under that recurring donation.

What version of the packages are you using?
NPSP 2.0

Please provide any additional information below.

Original issue reported on code.google.com by Fei.Xie...@gmail.com on 7 Jun 2013 at 3:19

Attachments:

• [07-06-2013 11-05-47.png](https://storage.googleapis.com/google-code-attachments/npsp/issue-354/comment-0/07-06-2013 11-05-47.png)
• [07-06-2013 11-09-08.png](https://storage.googleapis.com/google-code-attachments/npsp/issue-354/comment-0/07-06-2013 11-09-08.png)

[GoogleCodeExporter]

It depends on if you're creating an open-ended or non-open-ended recurring 
donation. I'd also need to know the package version (Setup-Installed Packages) 
for your Recurring Donations package.  

Its difficult to tell based on your screenshots, but this documentation may 
explain how things are supposed to operate: 
http://salesforcefoundation.screenstepslive.com/s/npsp/m/6170/l/58859-creating-n
ew-recurring-donations

Original comment by kbro...@gmail.com on 13 Jun 2013 at 2:16

[GoogleCodeExporter]

Hi Kevin,

Please see the screenshot for the version numbers we are using.
We have followed the steps in the documentation to create the recurring 
donations, and the fields looked correct after saving. The problem with the 
Installments field was actually caused by the nightly job, according to audit 
trail. The nightly job seemed to have put the the total number of opportunity 
lines in the batch to the last recurring donation record processed.

Best Regards,
Kevin Xie

Original comment by Fei.Xie...@gmail.com on 14 Jun 2013 at 4:58

Attachments:

• [6-14-2013 12-52-05 PM.png](https://storage.googleapis.com/google-code-attachments/npsp/issue-354/comment-2/6-14-2013 12-52-05 PM.png)

[GoogleCodeExporter]

Can you provide:

1. Your org ID
2. Login access to Salesforce.com support
3. A link to an example record that shows the incorrect behavior?

Thanks

Original comment by kbro...@gmail.com on 14 Jun 2013 at 1:39

[GoogleCodeExporter]

I have granted you access to the org, please find the details below-
Org Id: 00DO0000000YujT
Login: laputa@savethechildren.hk.demo

A sample data can be found here, you can see the "Installments" value changes 
in the audit trail related list:
https://cs5.salesforce.com/a08O0000003fwe0

Please let me know if you need other inputs.

Best Regards,
Kevin Xie

Original comment by Fei.Xie...@gmail.com on 17 Jun 2013 at 2:15

[GoogleCodeExporter]

Hi Kevin-

Unfortunately I'm unable to access sandbox environments for review. 

Thanks-
Kevin

Original comment by kbro...@gmail.com on 17 Jun 2013 at 2:12

[GoogleCodeExporter]

Hi Kevin,

I have granted you access to the production environment:
Org Id:00D90000000j0VU
Username: laputa@savethechildren.hk 

However there is no sample data available, as we have terminated the nightly 
job. The production is the running on the same versions and would have the same 
problem if the nightly job was turned on.

Thanks,
Kevin

Original comment by servi...@laputatech.com on 18 Jun 2013 at 2:29

[GoogleCodeExporter]

Looking at what's in the production org, its seems to be pretty close to 
correct, the installments are filled out as expected by the recurring 
operation. I understand though that the nightly job is currently not running 
though.  Were you finding the nightly job was updating the Opps in production 
as well?

Original comment by kbro...@gmail.com on 18 Jun 2013 at 1:52

[GoogleCodeExporter]

Yes, the nightly job was behaving incorrectly in production, same as in the 
sandbox. So we decided to turn it off temporarily.

Original comment by servi...@laputatech.com on 20 Jun 2013 at 2:00

[GoogleCodeExporter]

Ok, I'm able to access the sandbox now. I just set a an RD up, and then also 
turned off some of the workflow rules on RD (in sandbox) to give us a clean 
test.  

Original comment by kbro...@gmail.com on 20 Jun 2013 at 3:43

[GoogleCodeExporter]

Hi Kevin,

How did the test go? Can you provide an update?

Thanks,
Kevin Xie

Original comment by servi...@laputatech.com on 25 Jun 2013 at 11:04

[GoogleCodeExporter]

It looks like the sandbox was refreshed recently, or perhaps had the data 
removed?  There are no recurring donations currently in that SB.

Original comment by kbro...@gmail.com on 25 Jun 2013 at 2:32

[GoogleCodeExporter]

I think we deleted the data. Here is another example of wrong installments 
number:
https://cs5.salesforce.com/a08O0000003go2L

Feel free to create any data for test purpose, I will make sure we won't delete 
any data.

Original comment by servi...@laputatech.com on 27 Jun 2013 at 2:56

[GoogleCodeExporter]

So far, so good on the test RD I've created here: 
https://cs5.salesforce.com/a08O0000003gowD

I'll keep watching. 

Original comment by kbro...@gmail.com on 28 Jun 2013 at 2:29

[GoogleCodeExporter]

Hi Kevin, how did the test go? My client is waiting, can you please advise a 
time when this can be resolved?

Original comment by k...@laputatech.com on 4 Jul 2013 at 2:09

[GoogleCodeExporter]

Well, take a look:  https://cs5.salesforce.com/a08O0000003gowD

The installment field is correct after a week, so I'm not clear on what the 
issue is.  Until I can replicate the problem, there's no way to identify what 
the underlying cause is, and since nobody else is reporting it, I tend to think 
its likely something specific to your setup in your client's org.  I can 
continue to keep tabs on it, and if you can come up with steps to replicate 
what you're seeing, I'm happy to look at it again.  

Original comment by kbro...@gmail.com on 5 Jul 2013 at 4:02

[GoogleCodeExporter]

Hi Kevin, 

The issue can only replicate when there is a number of recurring donations set 
up for testing, say, 4 or 5. After the nightly job has run, one of the 
recurring donations will show an incorrect Installments number. Since this is a 
standard NPSP field, we haven't referenced this field anywhere in our own code.

I have attached the screenshot of the problem again.

I have also deleted all the existing recurring donations in the org so that you 
can have a clean test.

Original comment by Fei.Xie...@gmail.com on 22 Jul 2013 at 6:59

Attachments:

• issue.png

[GoogleCodeExporter]

So you're suggesting it will only manifest if I create 5-6 Recurring Donation 
records? Or 5-6 Opptys in a Recurring Donation?

Original comment by kbro...@gmail.com on 22 Jul 2013 at 1:21

[GoogleCodeExporter]

4-5 recurring donations

Original comment by Fei.Xie...@gmail.com on 23 Jul 2013 at 2:04

[GoogleCodeExporter]

I need you to re-extend logins for both Foundation and SFDC support for that SB 
and prod.

Original comment by kbro...@gmail.com on 26 Jul 2013 at 7:51

[GoogleCodeExporter]

Kevin, before moving forward, I have a question about the recurring donation 
batch process.
I tried to look up the documentation but I am still not clear:
http://salesforcefoundation.screenstepslive.com/s/npsp/m/6170/l/58865-understand
ing-the-batch-process-updating-donations

Under what condition will the nightly job generate new opportunities for the 
recurring donations? For example, if the Opportunity Forecast Month is set to 
be 24, will the nightly job generate opportunities for those recurring donation 
with less than 24 Pledge opportunities?

Thanks,

Original comment by Fei.Xie...@gmail.com on 31 Jul 2013 at 9:36

[GoogleCodeExporter]

24 would be the total number of months, not number of pledges. So if the 
Recurring Donation doesn't have 24 months worth of Opportunities (it could be 
24 if they're monthly, 8 if they're quarterly, etc.), then the nightly job will 
add Opportunities until there are 24 months worth of them available

Original comment by kbro...@gmail.com on 31 Jul 2013 at 1:33