2022.2

Skip over Source Data Records
AnotherveryimportantnewfeatureimplementedintheDataMapperistheabilitytoskipoversomeof
thesourcedatarecordswithoutwritinganythingtothedatabase.Thisallowsyoutoquicklyfilterout
somerecordsfromthedatasourcewithouthavingtoextractthemtothedatabasefirst,whilestill
extractingothers.(SHARED-24548)
Let’ssayforinstancethatyourdatasourcecontainspostaladdressesfrommanycountries,butyou
onlywanttoextractthedataforPortugal.Youcannowcreateaconditionthatexaminesthecountry
fieldtodetermineifthesourcerecordisforacountryotherthanPortugal.IftheconditionisFalse(i.e.
thecountryISindeedPortugal),youcanextractthedataasperusual.ButintheTruebranchofthecon-
dition(i.e.thecountryis anything butPortugal),youcannowaddanActionStepandspecifythenew
“Stop processing record”actiontype.Thisbasicallydiscardsthisdatarecordandinstructsthe
DataMappertoimmediatelyskiptothenextsourcerecord.
Thisyieldstwoimmediateandmajorbenefits:
l
DataExtractionismuchfastersinceyouareonlyextractingtherecordsyouactuallywant
l
Thedatabasewillnotbeclutteredwithuselessrecords(potentiallynumberinginthethousands)
thatyouwerenotgoingtouseanyway.Asaconsequence,theautomatedclean-upprocesswill
havemuchlessworktoperformwhenthetimecomestodeleteobsoleteentriesfromthedata-
base.Thisshouldresultinalighterworkloadandbetteroverallperformance.
Ifyoustopprocessinganyrecordafteryou’vealreadyextractedsomedatafromit,thenthe
recordwillstillbestoredinthedatabase,withun-extractedfieldsbeingassignedwhatever
defaultvalue(ifany)youdefinedforthem.Soifyourgoalistocompletelypreventunwanted
recordsfrombeingstoredinthedatabase,youshouldmakesuretoimplementyourfilteringcon-
ditionsearlyinthedatamappingprocess.
Improved naming of default fields
Thedefaultfieldnamingschemehasbeenenhancedtoallowduplicatefieldnamestobegenerated
automaticallyaslongastheyareondifferentlevels(orindifferentdetailtables).
ThisisespeciallyusefulwithXMLdatasourceswherefieldnames(e.g.,ID,NAME)areoftenre-used
throughdifferentlevelsofthestructure.
Withthenew,moreflexiblenamingscheme,theDataMapperchecksforduplicatesatthesamelevel
beforedecidingwhetherornottocreateorincrementanumericsuffixthatisappendedtothefield
name.(SHARED-42645)
Page 1511