|
Home > Archive > BizTalk Server General > September 2005 > mapping to repeating destination nodes
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
mapping to repeating destination nodes
|
|
|
| I have what I hope is a basic mapping question. I have a DESTINATION schema
that has an "Actor" node that can occur an unbounded number of times.
My SOURCE schema will have individual actors in separate nodes. For
example, the source will have a patient node, a physician node, a hospital
node, etc. Each of individual source nodes needs to map to one of the
repeating destination nodes.
Since the destination node only appears once in the mapper, I am unsure how
to map the individual source nodes. Any asistance would be appreciated.
Thanks.
| |
| Jan Eliasen 2005-09-12, 6:07 pm |
| On Sat, 10 Sep 2005 10:50:02 -0700, "DW"
<DW@discussions.microsoft.com> wrote:
>I have what I hope is a basic mapping question. I have a DESTINATION schema
>that has an "Actor" node that can occur an unbounded number of times.
>
>My SOURCE schema will have individual actors in separate nodes. For
>example, the source will have a patient node, a physician node, a hospital
>node, etc. Each of individual source nodes needs to map to one of the
>repeating destination nodes.
>
>Since the destination node only appears once in the mapper, I am unsure how
>to map the individual source nodes. Any asistance would be appreciated.
Hi
Just connect the elements. Drag from the pysician to the actor, drag
from the patient to the actor, and so on. It should work.
--
Jan Eliasen, representing himself and not the company he works for.
| |
|
| Thanks for the reply. Either I didn't explain my problem very well, or I
don't understand your suggestion (or both).
The destination "Actor" record occurs multiple times. One occurence could
be the from the Physician source record. Another occurence could be from the
Hospital source record. The source records populate different fields in the
destination. The source record structures don't match each other, or the
destination record. For example, the physician source record has a first
name field while the Hospital source record does not. The do share some
destination fields, for example "address". The point is, I need different
destination occurences for the individual source entities.
The simple solution would be to have a separate record for each destination
entity, and only have each destination record occur once. I would do that,
but since each destination record needs to be named "Actor", I think I have
to define a single record that occurs multiple times. When I try it, I get
an error indicating "an element with the same name exists in the current
scope...".
I have a solution that is kinda working using the table looping and table
extractor functoids. It's still not perfect and the map will be very complex
if I complete it this way. I guess I was hoping someone had a better
suggestion for me.
Thanks.
"Jan Eliasen" wrote:
> On Sat, 10 Sep 2005 10:50:02 -0700, "DW"
> <DW@discussions.microsoft.com> wrote:
>
> Hi
>
> Just connect the elements. Drag from the pysician to the actor, drag
> from the patient to the actor, and so on. It should work.
>
> --
> Jan Eliasen, representing himself and not the company he works for.
>
| |
| Jan Eliasen 2005-09-13, 7:48 am |
| On Mon, 12 Sep 2005 10:54:05 -0700, "DW"
<DW@discussions.microsoft.com> wrote:
>Thanks for the reply. Either I didn't explain my problem very well, or I
>don't understand your suggestion (or both).
Well, first we need to establish a common understanding of the problem
:-)
So, I have created this solution:
http://www.eliasen.dk/biztalk/TestM...nctionality.zip
Take a look at it. If I have misunderstood your problem, then try
attaching your two schemas and your map, and we'll take it from there.
--
Jan Eliasen, representing himself and not the company he works for.
| |
|
| Thanks Jan, that is exactly what I asked for!! Now for what I really want 
I followed your advice, and the actor nodes are being populated properly.
The one thing I failed to mention is that each actor record also has an
"ActorID" field. This is just a unique identifier for each actor record.
This Actor ID also needs be inserted elsewhere in the detination record to
point to the appropriate actor record.
So to build on your Output schema example, the output would look sonething
like:
Output
--PatientActorID
--PhysicianActorID
--Actor
----ActorID
----SSN
----Name
----Address
----Phone
I will try to figure this out, but if you have time to drop me a suggestion,
it would be appreciated. Thanks again!!
Dennis
"Jan Eliasen" wrote:
> On Mon, 12 Sep 2005 10:54:05 -0700, "DW"
> <DW@discussions.microsoft.com> wrote:
>
> Well, first we need to establish a common understanding of the problem
> :-)
>
> So, I have created this solution:
> http://www.eliasen.dk/biztalk/TestM...nctionality.zip
>
> Take a look at it. If I have misunderstood your problem, then try
> attaching your two schemas and your map, and we'll take it from there.
>
> --
> Jan Eliasen, representing himself and not the company he works for.
>
| |
|
| I think I have something that will work here. I have added a Script functoid
for each source record type. Each script has a single input from the source
record.
In the script, I just return a random number and assign the results to the
output schema. This seems to be giving me what I want. Thanks again.
"DW" wrote:
[vbcol=seagreen]
> Thanks Jan, that is exactly what I asked for!! Now for what I really want 
>
> I followed your advice, and the actor nodes are being populated properly.
> The one thing I failed to mention is that each actor record also has an
> "ActorID" field. This is just a unique identifier for each actor record.
> This Actor ID also needs be inserted elsewhere in the detination record to
> point to the appropriate actor record.
>
> So to build on your Output schema example, the output would look sonething
> like:
>
> Output
> --PatientActorID
> --PhysicianActorID
> --Actor
> ----ActorID
> ----SSN
> ----Name
> ----Address
> ----Phone
>
> I will try to figure this out, but if you have time to drop me a suggestion,
> it would be appreciated. Thanks again!!
>
> Dennis
>
>
>
>
>
> "Jan Eliasen" wrote:
>
|
|
|
|
|