Hi guys and ladies,
I'm using sdk for data map creation and import.
This is the scenario:
imported record has one lookup field referencing the entity itself.
Let's call this field New_lookup.
I have both "system" and "source" lookup mappings set up.
The lookup is resolved searching on a String property. Let's call this
New_externalid.
Now, if I'm importing a record that has a value on New_lookup that
references an invalid record, the transformation asyncservice creates an
Error Row with the message "cannot resolve lookup".
This is right.
EXCEPT in case the record I'm importing references a record that's not
imported. In this case, the transormation service gives an error "An
error has occurred. Try this action again.", but THE RECORD IS IMPORTED.
So you have a row with an error that gets imported.
Example:
New_externalid New_lookup Name
1 Name1 << Ok
2 1 Name2 <<
This lookup has a valid values. Ok
3 5 Name3 <<
Invalid values. Failure handled correctly
4 3 Name4 <<
Reference to a row with an error. FAILURE, BUT THE RECORD IS IMPORTED!
The problem wouldn't be so annoying if it would be possible to change
lookup values using an update import. But, as far as I know, update
imports do not process lookup mappings. They simply ignore them.
Please, could someone tell me if I'm doing something wrong? Except using
crappy import function, I mean.
Any help would be really appreciated.
By the way, did anyone tried to map a large (> 100 values) picklist? In
my experience, the import gives a Failure without further indications.
Someone could confirm?
Alberto Chiesa