IMPORTANT:
this is not a Support Forum! Experienced users might answer from time to time questions posted here. If you need a professional and reliable answer, or if you want to report a bug, please contact Altova Support instead.

Profile: island
About
User Name: island
Forum Rank: Advanced Member
Real Name: island_b
Location AT
Occupation: %2B
Interests:
Gender: None Specified
Statistics
Joined: Monday, October 28, 2002
Last Visit: Tuesday, November 27, 2018 5:50:55 AM
Number of Posts: 1,277
[7.46% of all post / 0.22 posts per day]
Avatar
Last 10 Posts
Topic: Running into error: Tutorial : SimpleType
Posted: Tuesday, November 27, 2018 5:50:16 AM
Hi,

if you expand the "Details" section in the Messages window it takes you to the pertinent part of the schema specification.

i.e.

Schema Component Constraint: Element Declarations Consistent
Code:

If the {particles} contains, either directly, indirectly (that is, within the {particles} of a contained model group, recursively) or ·implicitly· two or more element declaration particles with the same {name} and {target namespace}, then all their type definitions must be the same top-level definition, that is, all of the following must be true:

1 all their {type definition}s must have a non-·absent· {name}.
2 all their {type definition}s must have the same {name}.
3 all their {type definition}s must have the same {target namespace}.


Basically the two "State" elements have to be of the same type. If this were not the case there may be situations in which it is not clear whether a "State" element in the xml instance document should be validated according to the "State" element which is of type "string" or the "State" element of type "US-State".element.

+
Topic: Grouping on field value
Posted: Tuesday, November 13, 2018 10:23:45 AM
Try using the "group-starting-with" function



+
Topic: Conditional EDIFACT mapping
Posted: Thursday, November 8, 2018 11:30:12 AM
You will probably have to use two variables to hold the results of the different filters and then map the result of the variables to the output. If that doesn't help then attach your mapping and your input edi file

+
Topic: simple custom xslt function issue
Posted: Tuesday, October 23, 2018 10:34:18 AM
Hi,

only simple return types are supported for custom functions see documentation:

You can extend the XSLT 1.0 and 2.0 function libraries available in MapForce with your own custom functions, provided that your custom functions return simple types.

You can solve the the problem without having to use a custom xslt function however: See attached "test.mfd"



+
Topic: Map Excel Row and Col to XML
Posted: Friday, October 19, 2018 4:05:57 AM
and the third iteration is even better .....

+
Topic: Map Excel Row and Col to XML
Posted: Thursday, October 18, 2018 3:50:38 PM
Hi,

here is an even better variation without the need for an intermediate component.


+
Topic: Rename a connection?
Posted: Thursday, October 18, 2018 5:12:58 AM
Hi,

this is currently not possible but a feature request exists for this in Altova's internal wishes list

+
Topic: Map Excel Row and Col to XML
Posted: Thursday, October 18, 2018 5:01:29 AM
See attached mapping "test.mfd".

The mapping consists of two steps. The first step maps the excel source to an intermediate structure which outputs a file containing multiple "statPart" elements (see example_intermediate.xml).

The second step maps the intermediate structure to the ultimate target which generates only one "statPart" element as desired (see example_final.xml).

The intermediate component uses the "Duplicate Input" functionality to provide additional "cell" elements to map to.

Note the intermediate structure generates an output file in this mapping i.e. "example_intermediate.xml". This is simply to facilitate understanding of the example. Once you understand how it works you can replace the intermediate structure with a variable which does not generate an intermediate file (INSERT | Variable).


+
Topic: Map Excel Row and Col to XML
Posted: Wednesday, October 17, 2018 4:00:04 AM
HI,

please attach your Excel source file, your target xsd file(s) and the exact xml file that you wish to output from the given input Excel source data.



+
Topic: Altova_Hierarchical_DB.mfd only inserting one row when run from (debug) interface
Posted: Friday, October 12, 2018 4:51:00 AM
> I decided to run the "Altova_Hierarchical_DB.mfd". I get the same results. - only one row is being inserted in the Altova table.

This is what is expected in this example. The "Altova" element is connected to the "Altova" table. As the "Altova" source element only occurs once,
only one row will be inserted into the target "Altova" table.

With regards to your particular case: My guess is that you have not connected the correct element to the table. You need to connect the element in your source file which iterates twice so that two rows will be produced.

If you have connected the element which iterates twice to the target table and are STILL only getting one row in the database, then you might have to
disable the "Enable input processing optimizations based on min/maxOccurs" checkbox for you input xml component.





+

Use of the Altova User Forum(s) is governed by the Altova Terms of Use.