Received Amount of Contribution in Plans

I am trying to figure out how to have received amount of the contribution show up in Plans.  I was able to get it to show up in portfolio using TR_PORFOLIO_CUSTOMM_ELELMENT.  But am struggling how to set it up in T_Keyword to show up in the plan itself.  Does anyone already have this custom element setup who can lend me a hand?

Here are the field entries for TR_PORFOLIO_CUSTOMM_ELELMENT

Description:  Received Amt

Sql Query: Select Sum(recd_amt)From dbo.VS_CONTRIBUTION_WITH_INITIATOR where plan_no = @plan_no

Date Type: Currency

Parents
  • Hi Terry, 

    A couple things may be happening here:

    • If the plan was created after the contribution was entered into Tess, I have noticed that the auto-generated by the system received amount does not get added to the Plan. Instead we have to go into the contributions and manually enter the amount into the appropriate of the 3 editable cash fields within the plan.

    • The other consideration is to be sure that EVERYTHING you are selecting in your plan MATCHES the contribution entry exactly – Same campaign, designation, and fund combination. Many times (and I try to explain this to my team) I try to leave the Fund or Designation empty until it is absolutely necessary to enter something into those fields. It helps when you are tracking a donor who is giving to multiple funds or designations. Again, Tess is looking for a match, so if the field is populated in the Plan but does not match the contribution, it doesn’t get pulled in.

    But if you are referring to payments against a pledge ($500 toward a $2000 pledge), no, thats not built into the plan, and I am not sure how to customize that.

    Thanks,

    Marie

    ---

    Marie F. Kocher | Development Operations & Data Specialist

    Kansas City Ballet | Todd Bolender Center for Dance & Creativity

    500 W. Pershing Road, Kansas City, MO 64108

    816.216.5582 (D) | 816.931.2232 x1382 (O) | 816.931.1172 (fax)

    kcballet.org

Reply
  • Hi Terry, 

    A couple things may be happening here:

    • If the plan was created after the contribution was entered into Tess, I have noticed that the auto-generated by the system received amount does not get added to the Plan. Instead we have to go into the contributions and manually enter the amount into the appropriate of the 3 editable cash fields within the plan.

    • The other consideration is to be sure that EVERYTHING you are selecting in your plan MATCHES the contribution entry exactly – Same campaign, designation, and fund combination. Many times (and I try to explain this to my team) I try to leave the Fund or Designation empty until it is absolutely necessary to enter something into those fields. It helps when you are tracking a donor who is giving to multiple funds or designations. Again, Tess is looking for a match, so if the field is populated in the Plan but does not match the contribution, it doesn’t get pulled in.

    But if you are referring to payments against a pledge ($500 toward a $2000 pledge), no, thats not built into the plan, and I am not sure how to customize that.

    Thanks,

    Marie

    ---

    Marie F. Kocher | Development Operations & Data Specialist

    Kansas City Ballet | Todd Bolender Center for Dance & Creativity

    500 W. Pershing Road, Kansas City, MO 64108

    816.216.5582 (D) | 816.931.2232 x1382 (O) | 816.931.1172 (fax)

    kcballet.org

Children
  • Thanks Marie for that information.  I don't think I was completely clear that I have the received amount working perfectly in Portfolio using the setup I showed above. The problem is that I would also would like it to show in the Plans screen but I am uncertain how to complete the T_Keyword fields to make it work.  I know that the received amount needs to be summed for the plan_no from the VS_Constituent table but I don't know how to do a SUM in T_Keyword or if it is even possible.  Perhaps I need to create a view that sums the recvd_amt first and then use that in T_Keyword.  I have tried a few ways and the field is always zero but perhaps what you said above is the reason as these would all be plans which were created before I added that field.