Extraneous fields added in collection field mapping for attributes when importing

When an attribute is added to a constituent record via batch or import, there are several fields and values associated with the addition of that attribute - these include the attribute category, the value, start and end dates, comments, etc.  The set of fields associated with the addition of an attribute are called collection fields.  In an import process, these fields are all mapped as a separate group.  In some collection fields however, there appear to be additional, extraneous rows of information to map that are not part of the valid information for a given attribute.  For example, valid rows include:
 
<Attribute category> 1
<Attribute category> start date 1
<Attribute category> end date 1

But invalid rows are named "1" with no other information.

Download and install the latest version and patch, if applicable. 

Environment

 2.9.1001.116
 3.0.516

Was this article helpful?


Thanks for your feedback! Did this solve your issue?

Comments (optional):


Thanks for your feedback!
We're glad it was helpful but sorry it didn’t solve your issue. If you need assistance, click Chat with Support below.
We’re sorry to hear that. Please tell us why.

 I don't like how this works.

 The answer is confusing.

 The answer didn't match what I was searching for.

Additional Comments (optional):


Thanks for your feedback! If you need assistance, click Chat with Support below.
Thanks for your feedback. Help us make our products even better by sharing details in our Idea Banks or our online Community.
Thanks for letting us know. We'll work on clarifying the information in the article. If you need assistance, click Chat with Support below.
Thanks for letting us know. We'll work on updating the search engine to return more relevant results.