It’s a little hard to see what’s happening without the RecordMaps. Does the H record map specify a CRLF record terminator and does the data contain the right terminator? It is possible that if the terminator doesn’t match, the Record Map for the header considers the P1, OBR, and OBX records as part of the header. If that’s the problem, the complex record mapper won’t consider it an error because the P1, OBR, and OBX records are optional.
Is it possible to send the XML definitions of the complex record map and the record maps?
What version of Ensemble are you using? 2013.1?
One thing that I noticed was that the bread crumbs in the screen shot show “Ensemble, Record Mapper”, but it should show “Ensemble, Complex Record Mapper”.
I assume that the leading text for the record maps are “H”, “P”, “OBR”, “OBX”, and “L”.
--
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare Community" group.
To post to this group, send email to
Ensemble-in...@googlegroups.com
To unsubscribe from this group, send email to
Ensemble-in-Healt...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/Ensemble-in-Healthcare?hl=en
---
You received this message because you are subscribed to the Google Groups "InterSystems: Ensemble in Healthcare" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Ensemble-in-Healt...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
I generated RecordMaps using the CSV wizard and then created a complex record map. The message trace from the test production seems to show the P, OBR, and OBX records. I’ve included the XML for the message trace, record maps, complex record map, and production. In most cases I just used the default field names from the CSV wizard. I’m running 2013.1.
Let me know if this helps and what problems were in your record maps, complex record map, or production. I’ll make sure that the documentation covers that area sufficiently.
Good luck.
Joshua Goldman
Ensemble documentation
I’m including a few screen shots, but you should be able to import the XML files.
My complex record map is

The Header record map starts with

I don’t think I included the complex record map definition. This single export of the production contains all needed record maps and complex record map. You should be able to import the XML file and then start the production.
From: Joshua Goldman
Sent: Saturday, January 18, 2014 11:38 AM
To: Ensemble-in...@googlegroups.com
Cc: 'r.be...@solilog.fr'
Subject: RE: [InterSystems-EnsHlth] HPRIM Complex RecordMap
I generated RecordMaps using the CSV wizard and then created a complex record map. The message trace from the test production seems to show the P, OBR, and OBX records. I’ve included the XML for the message trace, record maps, complex record map, and production. In most cases I just used the default field names from the CSV wizard. I’m running 2013.1.
Let me know if this helps and what problems were in your record maps, complex record map, or production. I’ll make sure that the documentation covers that area sufficiently.
Good luck.
Joshua Goldman
Ensemble documentation
I’m including a few screen shots, but you should be able to import the XML files.
My complex record map is

The Header record map starts with

From:
Ensemble-in...@googlegroups.com [mailto:Ensemble-in...@googlegroups.com]
On Behalf Of Joshua Goldman
Sent: Friday, January 17, 2014 6:39 PM
To: Ensemble-in...@googlegroups.com
Subject: RE: [InterSystems-EnsHlth] HPRIM Complex RecordMap
It’s a little hard to see what’s happening without the RecordMaps. Does the H record map specify a CRLF record terminator and does the data contain the right terminator? It is possible that if the terminator doesn’t match, the Record Map for the header considers the P1, OBR, and OBX records as part of the header. If that’s the problem, the complex record mapper won’t consider it an error because the P1, OBR, and OBX records are optional.