Plugin:

Classic Connector for Salesforce & Jira

Question:

How Do I Resolve INVALID_FIELD Error When Performing Create/Update Actions?

Answer:

Problem

When you create or update a Case, you may experience an  "INVALID_FIELD" error.

The error in your server logs may look similar to the following:

2012-04-23 15:39:11,639 http-8500-5 WARN admin 939x58x1 epjwg7 127.0.0.1 /plugins/servlet/customware/connector/issue/1/Case/create.action [connector.salesforce.soap.SOAP] INVALID_FIELD: 
HasCommentsUnreadByOwner, Table__c, Table__r.Name, Dave_del__c, ContactId, Contact.Name
                                                   ^
ERROR at Row:1:Column:897
No such column 'Dave_del__c' on entity 'Case'. If you are attempting to use a custom field, be sure to append the '__c' after the custom field name. Please reference your WSDL or the describe call for the appropriate names.
2012-04-23 15:39:43,907 http-8500-6 WARN admin 939x78x1 epjwg7 127.0.0.1 /plugins/servlet/customware/connector/issue/1/Case/create.action [connector.salesforce.soap.SOAP] INVALID_FIELD: 
IsEscalated, IsClosed, JIRA_Subject__c, Dave_del__c, CaseNumber, ConfluenceField__c

 

This is because JIRA keeps all the remote fields in cache.

When any Salesforce.com custom field is deleted, updated or added, JIRA might still be keeping the old field in the cache.

During the JIRA ticket creation, it returns an "INVALID_FIELD" error because the deleted field no longer exists in Salesforce.com even though the field is not defined in your mapping.

Solution

  1. Go to JIRA Administration > Add-ons > Cloud Connectors > Mappings > Configure

  2. Look for the message "Can't see the field you want to map? Click Here"


     

  3. Follow the link. This action allows you to refetch the remote fields from your remote system (Salesforce.com).

    • Alternatively, you could restart your JIRA server.