- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-26-2022 09:00 AM
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.
Solved! Go to Solution.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-28-2022 06:43 AM
Hi,
When the one row is transformed, it looks for a coalesce field. It'll find the first one that's a match in your target table (since you have 2 or more, it's just going to grab one, could even be random of which one it does, but it queries for just 1 and goes with it).
It's only 1 transform process per 1 row (unless you have multiple transform maps for the same staging table, but that's a different conversation). The system does not take 1 row and then query for all matching serial numbers (for example) on the target table and then run over and over again per 'n' amount. It's just a 1 time run for that 1 row.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-28-2022 05:39 AM
Right...
that's the issue is that there's one row..
but i've got 2 records that should have coalesced (2 records with the same serial number).
so i expected it to update both records, but its only updating one and seems to ignore the other so just wondered if this is normal behavior?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-28-2022 06:43 AM
Hi,
When the one row is transformed, it looks for a coalesce field. It'll find the first one that's a match in your target table (since you have 2 or more, it's just going to grab one, could even be random of which one it does, but it queries for just 1 and goes with it).
It's only 1 transform process per 1 row (unless you have multiple transform maps for the same staging table, but that's a different conversation). The system does not take 1 row and then query for all matching serial numbers (for example) on the target table and then run over and over again per 'n' amount. It's just a 1 time run for that 1 row.
Please mark reply as Helpful/Correct, if applicable. Thanks!
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-28-2022 07:03 AM
ok, that is good to know as i thought otherwise (thought it would find all items that coalesce and update) - guess would need to perform that type of action via script, flow etc.
Thanks Allen

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-28-2022 07:09 AM
Hi,
You're welcome!
Please mark reply above as Correct, if applicable and any other as Helpful, if it was.
Take care! 🙂
Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!