Try DataDirect Cloud Now
skip to main content
Mapping tab options : Strip Custom Prefix
 

Strip Custom Prefix

The stripCustomPrefix map option applies to Microsoft Dynamics CRM data stores. These data stores treat the creation of standard and custom objects differently. Objects you create in your organization are called custom objects, and the objects already created for you by the data store administrator are called standard objects.
When you create custom objects such as tables and columns, Microsoft Dynamics CRM prepends a custom prefix (new_), a lowercase characters new immediately followed by an underscore to the name of the custom object. You can change the custom prefix, and define one or multiple prefixes for the same Microsoft Dynamics CRM instance.
For example, Microsoft Dynamics CRM creates a table named new_emp if you create a new table using the following statement:
CREATE TABLE emp (id int, name varchar(30))
You might expect to be able to query the table using the name you gave it, emp in the example. Therefore, by default, the DataDirect Microsoft Dynamics CRM Cloud map strips off the prefix, allowing you to make queries without adding the prefix new_. If you are using the setup dialog, use the Strip Custom Prefix parameter on the Mapping tab to control whether the map includes the prefix. If you are using the DataSource API, add stripCustomPrefix parameter to the Map Options connection parameter to to control whether the map includes the prefix:
For example, a Microsoft Dynamics CRM user who creates a custom object named emp might expect to be able to query the table using the name they gave it. Therefore, by default, the DataDirect Microsoft Dynamics CRM Cloud map strips the prefix, allowing the user to make queries without adding the prefix new_. To strip multiple prefixes, add them as comma-separated values, for example: new,test,abc.
Value
Result
(unspecified)
new_ is stripped.
Comma-separated string, for example, new,test,abc
The specified prefixes are stripped.
<none>
The angle brackets are required for this special value. If you are disabling the option via an XML-based configuration, you must explicitly add the value as &lt;none&gt;
No prefixes are stripped.
The first time you save and test a connection, a map for that data store is created. Once a map is created, you cannot change the map options for that Data Source definition unless you also create a new map. For example, suppose a map is created with this parameter set to new,test. Later, you change the value to new,abc. You will get an error saying the configuration options do not match. Simply change the value of the Create Map option to force creation of a new map.