Selecting None on a column mapping still stores the original column name

Hi there,

When I set up a job and choose None for the source column (and map it to a constant) it still stores a column name in the job XML. That causes some unnecessary overhead in the OData provider as it still uses that column in the select statement.

For example, I have this job mapping:

But the Job XML has this for the last two columns:

<columnMapping>
  <scriptType>Constant</scriptType>
  <scriptValue>true</scriptValue>
  <isKey>False</isKey>
  <isActive>True</isActive>
  <scriptValueForInsert>False</scriptValueForInsert>
  <sourceColumn>NPR_Search</sourceColumn>
  <destinationColumn>ProductImportedFromOData</destinationColumn>
</columnMapping>

The NPR_Search column is assigned even when I create a new column mapping and select None.

For the job itself it's not an issue, but the source columns are used to build up the GET URL in an OData source. For example, the mapping above leads to the following URL:

?$select=No%2CDescription%2CNPR_Search%2CNPR_Search

which brings back that NPR_Search column unnecessarily.

Thanks in advance for looking into this.

Imar

Developer forum

Selecting None on a column mapping still stores the original column name

Replies