Transform map - what happens if target field is not existing?

[Bart Z]

Hi 🙂 Is anyone sure what happens if transform map fields are not matching, because target field is simply not existing in dictionary?

import set table field: u_XXX

target field: u_XXX (not present in dictionary)

is it just ignored? Or maybe it is somehow created or inserted with unknown data type or anything?

[Bart Z]

It's made after copying the whole transform map and changing the target table. Mapping is a bit too complicated to figure it out on my own, so I am trying to just use all existing ones, and make those that are not matched ignored 🙂 thanks!

[shloke04 · Accepted solution]

I see you have marked an answer as correct, but I believe that is a partially answer as that error will not throw up all the time for every incorrect mapping.

To make it clear, let's say when you are defining a Field Map you need to select a field in the Target column and say for example I have mapped Category to Short Description, it will not thrown any error and it will map it across to Short Description field.

There can be error message which will come up when you are trying to map a field which are not of same Dictionary Type.

Which means in Source Field you are having it as a String and in Target you are trying to map this to a Different field Type say Boolean then it will not work

In short, Along with this for different scenario there can be different error message coming up and not just 1 specific highlighted above.

Hope this helps. Please mark the answer as correct/helpful based on impact.

Regards,
Shloke

[Sulabh Garg]

@shloke04  - In the original ask, Bartłomiej explicitly mentioned "target field is simply not existing in dictionary" , and he is not asking all types of incorrect mapping. And I tried the same scenario on my PDI and gave the screenshot. 

I am fine if your answer is marked as correct, But we should not confuse the user who actually faces the issue to mark the question as correct or not. Let user decide this part..

Thanks, 

[shloke04]

@Sulabh Garg 

My Point was responding again to the post due to reason below:

1) If the Target field does not exist then why are you trying to map it even? If it does not exist make sure to remove that from the Field mapping why to have records created which are not adding value and just error logs to the system?

Any use case you can think of why the field map should be still defined? Intent here which I initially responded was to understand what is the use case here which author is trying to resolve. Please read my initial reply first.

Also to note when a new Field Map is created there is always some value in target field may be not the correct field which we are trying to map but by default in OOB some field is by default selected. So ServiceNow will try to map it to that and there can be mismatch error and different error thrown for the same.

I don't understand what is your point here and where I am trying to confuse the author. I have just tried to make it clear for the author by sharing more details.

Regards,

Shloke

[Sulabh Garg]

@shloke04 - My point is user has specifically mentioned that target field is not present in the dictionary then what would happened? I agree with your point there is no use case why you want to create a field map. However there could be scenario wherein field map was created before and then target field was removed due to any reason. In that case what would happen, system (OOB) will not delete the field map, correct. And it will throw the error as I mentioned in my comment.

Moreover, author was also convinced on the answer and he marked the answer as correct, However you mentioned its partially answered, I don't get this point and it will unnecessary confuse the author.

Lets not drag this and I am glad we were able to answer the questions post on the community. 🙂 Cheers.!!