Hi Oli,
The Siebel Datamapper is indeed powerful, but some years ago I came across a requirement which I could not achieve using declarative approach, and had to fallback to scripting the property sets.

Here is a rough explanation.

This is the incoming source XML from the end system:

<root>
	<Quarter>
		<profit q="1">80</profit>
		<profit q="2">90</profit>
		<profit q="3">70</profit>
		<profit q="4">85</profit>
	</Quarter>
	<Quarter>
		<profit q="1">80</profit>
		<profit q="2">90</profit>
		<profit q="3">70</profit>
		<profit q="4">85</profit>
	</Quarter>
	<Quarter>
		<profit q="1">80</profit>
		<profit q="2">90</profit>
		<profit q="3">70</profit>
		<profit q="4">85</profit>
	</Quarter>
	<Quarter>
		<profit q="1">80</profit>
		<profit q="2">90</profit>
		<profit q="3">70</profit>
		<profit q="4">85</profit>
	</Quarter>
</root>



And this had to be mapped to this target in Siebel :


<root>
	<Quarter>
		<q1>80</q1>
		<q2>90</q2>
		<q3>70</q3>
		<q4>85</q4>
	</Quarter>
	<Quarter>
		<q1>80</q1>
		<q2>90</q2>
		<q3>70</q3>
		<q4>85</q4>
	</Quarter>
	<Quarter>
		<q1>80</q1>
		<q2>90</q2>
		<q3>70</q3>
		<q4>85</q4>
	</Quarter>
	<Quarter>
		<q1>80</q1>
		<q2>90</q2>
		<q3>70</q3>
		<q4>85</q4>
	</Quarter>
</root>


Basically in the source, under each quarter, this is one one record (for the lack of a better term) for each quarter, so 4 records. But in the target, there is only record for the entire year , with 4 different fields corresponding to each quarter. So this is a row-to-column conversion.

Maybe I missed something back then, but can this kind of mapping be achieved using declararive datamappers and NO scripting ?

Thanks

cleartext.blogspot.com