Import Fields

I exported my opportunities, updated some values without touching column headers, went to import it back in (since global editing is not available with opportunities) and there are fields with NO MATCH. How can that be?

0

Comments

3 comments
  • Hi Victor,

    Occasionally the importer will not recognize your field headers automatically.  In those instances, all you need to do is click on the "No Match" fields and manually map them to your Insightly account.

    0
    Comment actions Permalink
  • Hi Dan, That doesn't work, they aren't in the drop downs and I think I know why. They are fields that Insightly allows users to add to, such as Opportunity State Reasons (which shows up as (LastChangeStateReason), which is one of the problem fields, and a key field I was updating. Also problematic are standard fields such as DateCreated, DateOfLastActivity and DateOfNextActivity. I suppose I could select "Do not import this field", hope that none of what is there already changes and fix the State Reasons manually one by one.

    Thanks, Victor

    0
    Comment actions Permalink
  • Hi Victor,

    You're correct, the fields you've mentioned cannot be updated using the import function.  The DateCreated, DateOfLastActivity and DateOfNextActivity fields are all automatically set by the system and cannot be manually edited, but there is a feature request to add the ability to update the Opportunity State Reason to our import system that I would recommend you add your vote to on our Ideas and Suggestions page.

    0
    Comment actions Permalink

Please sign in to leave a comment.