We're importing a handful of custom fields to the NPSP Data Import object, then using the Start Import button to copy those values over to the various objects (mostly to Opportunity object fields). We're getting an error "Illegal assignment from string to decimal" when importing many of these custom fields. The weird thing is we're importing to fields that are data type = text area, so I'm not sure where the "string to decimal" conversion is coming into play. The last error we saw was for a conversion to a date field.
Anyone else seeing these errors?
@Nonprofit Success PackI just ran into a similar issue this Monday. I am getting "Illegal assignment from Date to String" when trying to populate custom Date fields on the Contact object.
Contacts object has two custom Date fields:
EAH_Legacy_Date_Entered__c
EAH_Legacy_Last_Update__c
NPSP Data Imports object has corresponding Date fields:
EAH_Contact1_Legacy_Date_Entered__c
(help text Contact1.EAH_Legacy_Date_Entered__c)
EAH_Contact1_Legacy_Last_Update__c
(help text Contact1.EAH_Legacy_Last_Update__c)
EAH_Contact2_Legacy_Date_Entered__c
(help text Contact2.EAH_Legacy_Date_Entered__c)
EAH_Contact2_Legacy_Last_Update__c
(help text Contact2.EAH_Legacy_Last_Update__c)
I am able to successfully insert the records into the NPSP Import Object using Data Loader, with dates formatted to yyyy-mm-dd in Excel. But when I click Start Data Import in NPSP, any records that have data in those two fields are marked as "Illegal assignment from Date to String" (although a small percentage of them - less than 1% -
somehow seem to still result in a Contact record despite the failure on their Import Object record). When I delete those columns from the .csv everything gets populated properly and there are no errors (but also no data in those fields, obviously).
I have not encountered this issue before this Monday, even though I have used NPSP Data Import process before.
