This content has been marked as final. Show 6 replies
This sounds like an instance where the source value - that is the field to be mapped - that is created by the import format definition does not match the mapping table that you have defined. Check that the import format is correct and verify that the source value (on the import screen) is appearing as you would expect it to.
the 1:1 maps need to be in Explicit then the default rule needs to be in Like, that will ensure that FDM tries to map the 1:1's first.
You need to test that your 1:1's are working...delete the rule for the default code and import data.
Thanks for the reply...Let me see that works...!!!
Thank you – we have mapped all items as explicit but those that should be mapped to our default project code are rejecting (even though it is explicitly mapped). We have successfully loaded the mapping file with no errors, therefore we assume the format of this to be correct. Is there a place in FDM where old mappings are stored that the system is trying to read from?
FDM does store the maps that were applied but it does not ever use those to perform mapping.
You said you loaded the mapping table. Is there a chance that your mapping table contains a space in the mapping definition? Ex: Instead of source value = "12345" it is actually "12345 ".
Also, did you check the import format as I previously suggested?
Thanks for your Valuble response...We had missed to add the prefix and its working fine...Once again thanks for your response....!!!!