tMicrosoftCrmInput

tMicrosoftCrmInput Properties

Component family	Business / Microsoft CRM
Function	This component retrieves data from an entity of a Microsoft CRM database.
Purpose	This component allows you to extract data from a Microsoft CRM database based on conditions set on specific columns.
Basic settings	Authentication Type	Select the authentication type that corresponds to your specific CRM deployment model. ON_PREMISE: The CRM is installed in-house on the customer’s own servers, and licensing is purchased along with any necessary infrastructure. ONLINE: The customer accesses the CRM as part of a cloud-based subscription service, hosted by Microsoft in their data centers.
	Microsoft WebService URL	Type in the webservice URL of an on-premise Microsoft CRM server. This field appears only when ON_PREMISE is selected from the Authentication Type drop-down list. In this case, the Microsoft CRM API version supported is v2007 and this field can be filled with the URL like this: http://ServerAddress/MSCrmServices/2007/CrmService.asmx.
	API Version	Select a Microsoft CRM API version from the drop-down list. The version may be v2007 or v2011. This field appears only when ONLINE is selected from the Authentication Type drop-down list.
	OrganizeName	Enter the name of the user or organization, set by an administrator, that needs to access the Microsoft CRM database.
	Username and Password	Type in the webservice user authentication data. To enter the password, click the […] button next to the password field, and then in the pop-up dialog box enter the password between double quotes and click OK to save the settings.
	Domain	Type in the domain name of the server on which the Microsoft CRM is hosted. This field appears only when ON_PREMISE is selected from the Authentication Type list.
	Host	Type in the IP address of the Microsoft CRM database server. This field appears only when ON_PREMISE is selected from the Authentication Type list.
	Port	Type in the listening port number of the Microsoft CRM database server. This field appears only when ON_PREMISE is selected from the Authentication Type list.
	Discovery service endpoint	Specify the CRM online discovery service endpoint. This field appears only when ONLINE is selected from the Authentication Type drop-down list.
	Time out (second)	Specify the number of seconds to wait for a reply message from the CRM server before closing the connection with it.
	Entity	Select the relevant entity from the list. If needed, select CustomEntity from the list, then specify an entity name in the Custom Entity Name field and define the schema for the custom entity.
	Custom Entity Name	Specify the name of the custom entity. This field appears only when CustomEntity is selected from the Entity drop-down list.
	Schema and Edit schema	A schema is a row description. It defines the number of fields to be processed and passed on to the next component. The schema is either Built-In or stored remotely in the Repository. Since version 5.6, both the Built-In mode and the Repository mode are available in any of the Talend solutions. Click Edit schema to make changes to the schema. If the current schema is of the Repository type, three options are available: View schema: choose this option to view the schema only. Change to built-in property: choose this option to change the schema to Built-in for local changes. Update repository connection: choose this option to change the schema stored in the repository and decide whether to propagate the changes to all the Jobs upon completion. If you just want to propagate the changes to the current Job, you can select No upon completion and choose this schema metadata again in the [Repository Content] window. Click Sync columns to retrieve the schema from the previous component connected in the Job. Note In this component the schema is related to the selected entity.
	Logical operator used to combine conditions	Select the logical operator used to combine the conditions defined in Conditions table. Two operators are available: And: the record will be included in the result set when all of the conditions are met. Or: the record will be included in the result set when any of the conditions is met.
	Conditions	Click the [+] button to add as many conditions as needed. The following parameters need to be set for each condition: Input column: Click in the cell and select the column of the input schema on which the condition is to be set. Operator: Click in the cell and select the operator used to compare the value for the input colulmn with the value defined in the Value column. The values for this parameter are: Equal, NotEqual, GreaterThan, LessThan, GreaterEqual, LessEqual, and Like. Value: Type in the value between quotes if needed.
Advanced settings	tStatCatcher Statistics	Select this check box to gather the Job processing metadata at a Job level as well as at each component level.
Global Variables	NB_LINE: the number of rows read by an input component or transferred to an output component. This is an After variable and it returns an integer. ERROR_MESSAGE: the error message generated by the component when an error occurs. This is an After variable and it returns a string. This variable functions only if the Die on error check box is cleared, if the component has this check box. A Flow variable functions during the execution of a component while an After variable functions after the execution of the component. To fill up a field or expression with a variable, press Ctrl + Space to access the variable list and choose the variable to use from it. For further information about variables, see Talend Studio User Guide.
Usage	This component is usually used as a start component and it requires an output component.
Limitation	This component supports Microsoft CRM 4.0 (2007) for the On-Premise authentication type and Microsoft CRM 4.0 (2007) and 2011 for the Online authentication type.

Scenario: Writing data in a Microsoft CRM database and putting conditions on columns
to extract specified rows

This scenario describes a four-component Job which aims at writing the data included
in a delimited input file in a custom entity in a MicrosoftCRM database. It then
extracts specified rows to an output file using the conditions set on certain input
columns.

Warning

If you want to write in a CustomEntity in Microsoft CRM database, make
sure to name the columns in accordance with the naming rule set by Microsoft,
that is “name_columnname” all in lower case.

Setting up the Job

Drop the following components from the Palette to the design workspace: tFileInputdelimited, tFileOutputDelimited, tMicrosoftCrmInput, and tMicrosoftCrmOutput.
Connect tFileInputDelimited to tMicrosoftCrmOutput using a Row Main connection.
Connect tMicrosoftCrmIntput to tFileOutputDelimited using a Row Main connection.
Connect tFileInputDelimited to tMicrosoftCrmInput using OnSubjobOk connection.

Configuring tFileInputDelimited

Double-click tFileInputDelimited to
display its Basic settings view and define
its properties.
Set the Property Type to Repository if you have stored the input file
properties centrally in the Metadata node
in the Repository tree view. Otherwise,
select Built-In and fill the fields that
follow manually. In this example, property is set to Built-In.
Click the three-dot button next to the File
Name/Input Stream field and browse to the delimited file that
holds the input data. The input file in this example contains the following
columns: new_id, new_status,
new_firstname, new_email,
new_city, new_initial and
new_zipcode.
In the Basic settings view, define the
Row Separator allowing to identify the
end of a row. Then define the Field
Separator used to delimit fields in a row.
If needed, define the header, footer and limit number of processed rows in
the corresponding fields. In this example, the header, footer and limits are
not set.
Click Edit schema to open a dialog box
where you can define the input schema you want to write in Microsoft CRM
database.
Click OK to close the dialog box.

Configuring tMicrosoftCrmOutput

Double-click tMicrosoftCrmOutput to
display the component Basic settings view
and define its properties.
Enter the Microsoft Web Service URL as well as the user name and password
in the corresponding fields.
In the OrganizeName field, enter the name
that is given the right to access the Microsoft CRM database.
In the Domain field, enter the domain
name of the server on which Microsoft CRM is hosted, and then enter the host
IP address and the listening port number in the corresponding fields.
In the Action list, select the operation
you want to carry on. In this example, we want to insert data in a custom
entity in Microsoft Crm.
In the Time out field, set the amount of
time (in seconds) after which the Job will time out.
In the Entity list, select one among
those offered. In this example, CustomEntity is
selected.

Note

If CustomEntity is selected, a Custom Entity Name field displays where you
need to enter a name for the custom entity.

The Schema is then automatically set
according to the entity selected. If needed, click Edit schema to display a dialog box where you can modify
this schema and remove the columns that you do not need in the output.
Click Sync columns to retrieve the schema
from the preceding component.

Configuring tMicrosoftCrmInput

Double-click tMicrosoftCrmInput to
display the component Basic settings view
and define its properties.
Set the Property Type to Repository if you have stored the input file
properties centrally in the Metadata node
in the Repository tree view. Otherwise,
select Built-In and fill the fields that
follow manually. In this example, property is set to Built-In.
Enter the Microsoft Web Service URL as well as the user name and password
in the corresponding fields and enter the name that is given the right to
access the Microsoft CRM database in the OrganizeName field.
In the Domain field, enter the domain
name of the server on which Microsoft CRM is hosted, and then enter the host
IP address and the listening port number in the corresponding fields.
In the Time out field, set the amount of
time (in seconds) after which the Job will time out.
In the Entity list, select the one among
those offered you want to connect to. In this example,
CustomEntity is selected.
The Schema is then automatically set
according to the entity selected. But you can modify it according to your
needs. In this example, you should set the schema manually since you want to
access a custom entity. Copy the seven-column schema from tMicrosoftCrmOutput and paste it in the schema
dialog box in tMicrosoftCrmInput.
Click OK to close the dialog box. You
will be prompted to propagate changes. Click Yes in the popup message.
In the Basic settings view, select
And or Or as the logical operator you want to use to combine the
conditions you set on the input columns. In this example, we want to set two
conditions on two different input columns and we use And as the logical operator.
In the Condition area, click the plus
button to add as many lines as needed and then click in each line in the
Input column list and select the column
you want to set condition on. In this example, we want to set conditions on
two columns, new_city and new_id.
We want to extract all customer rows whose city is equal to “New York” and
whose id is greater than 2.
Click in each line in the Operator list
and select the operator to bind the input column with its value, in this
example Equal is selected for
new_city and Greater
Than for new_id.
Click in each line in the Value list and
set the column value, New York for
new_city and 2 for
new_id in this example. You can use a fixed or a
context value in this field.

Configuring tFileOutputDelimited

Double-click tFileOutputdelimited to
display the component Basic settings view
and define its properties.
Set Property Type to Built-In and then click the […] button next to the File
Name field and browse to the output file.
Set row and field separators in the corresponding fields.
Select the Append check box if you want
to add the new rows at the end of the records.
Select the Include Header check box if
the output file includes a header.
Click Sync columns to retrieve the schema
from the preceding component.

Job execution

Save the Job and press F6 to execute it.

Only customers who live in New York city and those whose “id” is greater than 2
are listed in the output file you stored locally.

Document get from Talend https://help.talend.com

Thank you for watching.

Docs 5.x

0 Comments

Inline Feedbacks

View all comments

tMicrosoftCrmInput – Docs for ESB 5.x