Should import set transform map update all Coalesce target records?

[Les1]

So i did searching around docs & community and couldnt resolve this question:   is it expected that during a transform map, all target records that the coalesce field matches will be updated?

example: doing an import test against hardware assets (alm_hardware)  and just have a couple of target records i would expect to be updated based on a coalesce field on Serial number. However, the result is that one record gets updated and the other seems ignored. In my very simple test case, the field i'm expecting updated is "asset tag."

So i wondered if the transform map only updates the first record it finds?  I will also say that the record that is not being updated was created by our MIDSERVER, i believe from sccm plugin activity (so maybe theres a blockage there?) and if so where do i go next in isolating the cause. mainly just trying to understand for sure the expectation.

[Allen Andreas]

Hi,

Just to clarify...you picking a coalesce field or fields...is merely a way to prevent "duplication".

It is not a guarantee that those records will in fact get updated.

It's just saying hey...I have 50 records in my staging table, search the target table for it's match (via serial, in your case). Say 40/50 match. So 10 don't...you can elect what to do with those 10 (ignore or create new, etc.).

But back to the main point, so say you ignore those 10 and we work with the 40...after that, you have other field mappings that take place and onAfter scripts, etc.

You also have "run business rules" either true or false to run on the transform map as well.

So even if a match is found, it may not be updated...if all the information remains the same.

As far as "seems to be ignored", you'd need to verify that. You can go to your staging table, look at the row relevant to this scenario, look at the state field, what does it say?

Please mark reply as Helpful/Correct, if applicable. Thanks!

[Les1]

Interesting if i'm understanding you right Allen, you're saying that an import set will not necessarily update every target record that matches the coalesce field?

in my test example i just have two records that both have the same serial number, the coalesced field.

so the import set (see below) just shows an "ignored 1" which i presume is the record that was updated prior (i've re-tried the import a few times) .. and i do have 'run business rules' unchecked. As otherwise, i'd expect something referring to TWO records right? 

I appreciate the feedback all, just making sure i understand the expectation of platform behavior.

[Allen Andreas]

Hi,

When you go to the import set associated with the above screenshot, do you see two rows listed?

[Les1]

just one row

[Allen Andreas]

Hi,

Ok, so then there's only 1 row being transformed then...?

So then that's why you see 1 result in the outcome per your screenshot.

Please mark reply as Helpful/Correct, if applicable. Thanks!