Setting up the CRM Export (Internal Only)

Which CRM objects does the client want to export?

• Remove all DSS tasks that are associated with CRM objects that the client is not going to export.
• For example, we rarely see clients exporting Financial Aid data. In this case, remove the TargetX CRM export - FinAid - step1 v2 and TargetX CRM export - FinAid - step2 v2 DSS tasks from the TargetX CRM export v2 flow.

Identify what updates would cause the Contact record to be in the export

• The TargetX_Datab__Ready_To_Export_Date__c field referenced earlier in the documentation is meant to be used as the main data filter on the TargetX CRM Export - Contact v2 DSS task. This field should be updated based on the client's requirements.
• For example, suppose a client wants to export a Contact every time an Application Decision is updated on an Application record. In that case, you will need to create a cross-object Workflow to update the Contact object's Ready To export Date field.

Identify other object data filters

• A client may only want certain child records exported for the Contacts.
• For example, when a Contact is exported, the client may only want to export SAT or ACT test scores. In this use case, you would set a data filter on the TargetX CRM export - TestScore - step1 v2 DSS task to include only SAT and ACT test types.
• All data filters should be set on step 1 of each DSS task. Step 2 is reserved for excluding records where the Contact Id IS NULL.

Review the post-processing commands

• Each DSS Task that produces the final export file for each object will have a post-processing command that looks like this:

COPY C:\Informatica\TargetX\dropbox\crmexport_application.csv C:\Informatica\TargetX\archives\export\^"crmexport_application_%DATE:/=-%.csv^" & COPY C:\Informatica\TargetX\dropbox\crmexport_application.csv C:\Informatica\TargetX\crm_export\application\crmexport_application.csv

• This post-processing command will copy the crmexport_application.csv export file, for the Application object, to both the archives directory and a new directory called crm_export\<object name>.
• This is very important if the client uses Axiom because Axiom requires each object's file to have its own directory (see below).

• This directory structure is not required if the client is not using Axiom.
• However, you must adjust the post-process command in the Contact export and all step 2 tasks.