Header image

Many clients have asked us in the past if they can utilize recurring batches for cash receipts. This is a more simplistic and flexible way of achieving what can also be done through a scheduled payments transaction. Dynamics GP 2010 now offers this capability.

The batch can be setup just like a GL recurring batch by updating the drop down menu for the Frequency field (shown in the screenshot below). The amount in the Recurring Postings field (shown in the screenshot below) indicates how many times this batch will be available for posting. Each time the batch is posted, the transaction dates are updated, but the cash receipt transaction amounts within the batch stay the same. If utilizing the EFT module, EFT Cash Receipt transactions can also be entered in recurring batches.

Furthermore, GL Recurring batches have been updated in Dynamics GP 2010 as well. The new feature that has been added enables the user to Clear Recurring Amounts for Recurring batches after posting. This can be accomplished by simply checking the checkbox next to Clear Recurring Amounts in the batch entry window (screenshot shown below). This feature is similar to Quick Journals, but is more customizable. This feature helps to decrease data entry errors by allowing common journal entries to be created with ease. In addition, this feature prevents a user from accidentally posting a recurring batch without making necessary changes as the batch will not post until the user updates the amounts for the journal entry.

GP 2010 GL Batch Entry

 

Out of the box, Microsoft Dynamics CRM 2011 does provide a Revenue Generated by Marketing Campaign Chart and View; however it does not copy that Actual Revenue amount to a field on the Campaign Form. A recent client wanted to have this field on the Campaign Form in order to perform some ROI calculations (using Java script) on the Campaign Form. We accomplished this goal with these steps:

1. First, create a new field (currency) on the Campaign Form.
2. Create a process workflow on the Opportunity entity that updates the Source Campaign tied to a given Opportunity.

a. Scope = Organization
b. Start when = Record status Changes
c. Add Check Condition Step = Opportunity Status equals [Won]
d. If condition is met Add Step = Update: Source Campaign
e. Click on Set Properties

f. The Campaign form will open
g. Click in the Actual Revenue field (that was created in Step 1)
h. Select Operator: Increment by
i. Look for: Opportunity
Actual Revenue
j. Click on Add

3. Close and Activate the workflow
4. Now, every time an opportunity tied to a Source Campaign is won, the Actual Revenue amount gets incremented/added in that Source Campaign form.

This is just one of the uses of the “increment by” feature in workflows. It obviously can be used to update other numerical /date fields on related entities. There is also an option to “decrement by” and “multiply by” which is also very useful.