Originally posted by: SystemAdmin

Hi Mercator fans!

Been away from mapping for a while and just got 6.7 with schema importer. Couple of questions (and pardon my atrophied mapping skills):

1) Why doesn't schema importer support namespaces. I was able to manually create namespace tree that seems to work fine. Seems like it would be an easy addition to schema importer.

2) The Importer created schema tree doesn't seem to like to validate choice groups that are optional that appear after a required group. It places the choice group into a parent group with range of (0:1). Validation fails unless I remove the parent group and make the choice group required. Hmmm.

3) How the heck do you map to the membes of a choice group on output. I need to create one of the choice group's members based on a value in the input but it could produce any of the members. As soon as I enter a rule, the other members "just say no" to any additional rules.

Other than that, gotta love Mercator and XML. Just get a really big screen and crank up the resolution!
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Re (3): You can pick any one of them to map to (unless you are using a data audit on output) since the output will not be validated, OR, change the tree and add a generic element at the end of the choice group whose values are either unrestricted (if the tree will only be used for output), or includes any of the values allowed for the other choices.

If you are talking about a supplied tree (I.e. X12, HIPAA, etc.), I would recommend against creating a customized version of the tree.
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Thanks for the tips. Unfortunately, my input is a code with values of A-F and each letter requires me to build a different member of the choice group on output. Basically, I need the choice group to act like partitioned type on output.

And I was really hoping I could use the same schema tree to validate input and build output.

I guess I can always try the really ugly solution: a functional map that conditionally calls one of six functional maps (each building a different member of the choice group), depending on the value in the input.

This just seems like a really awkward way to handle XML choice groups as output. I would expect to be able to enter rules into each member of a choice group and have Mercator step through the evaluations from top to bottom. First one that doesn't evalute to NONE gets built and the rest of the members are skipped.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange