| island |
| Newbie |
| island_b |
| AT |
| %2B |
|
| None Specified |
|
| Monday, October 28, 2002 |
| Tuesday, October 29, 2019 9:36:48 AM |
1,283
[7.09% of all post / 0.16 posts per day] |
|
Hi,
ensure that you have "Cast values to target types" unchecked:
https://www.altova.com/manual/Mapforce/mapforceenterprise/mff_xml_component_settings.htm?zoom_highlightsub=cast%2Bvalues
+
|
Hi,
XSLT has no control over which printer tray the result of an xslt transformation is sent to.
+
|
The Flowforce engine was rewritten for version 2019. Therefore you should follow the advice given and download and install the latest available version (2019sp1).
+
|
Hi,
please contact support and provide them with your sps file, your working xml file and xml schema(s).
+
|
Hi,
I assume that this is supposed to be the header of the file:
Code:
Carrier Rate Type Origin Market Origin Country Origin Place Name Origin Dest Market Dest Country Destination Place Name Dest Eff.From Eff.To Equipment Currency Lump Sum Charge Code Charge Name Charge Description Commodity Charge Basis Comments 1 Transit Time Principal Client Name Consignee Consignee Name Consignor Consignor Name Agent Agent Name Movement.Terms Client Type/Group Port Origin Port Dest Carrier2 Carrier Name Clearance Agent Clearance Agent2 Maximum Sailing Schedule Department Supplier Analysis Charge Filt3 Analysis Charge Filt
and these are the values corresponding to the headers:
Code:
MAR fak 40HC USD 103 oce-ebaf CONTAINER
seeing as both are space delimited this would infer that "Mar" is a Carrier, "fak" is a Rate, "40hc" is a Type, "USD" is an Origin, "103" is a Market, "oce-ebaf" is another "Origin" (???) and "CONTAINER" is a country.
This doesn't make sense. Please CLARIFY WHICH HEADER each of these values is supposed to correspond to.......
(It may help if you attach the source file you are dealing with. You can attach the file by first POSTING a response and then using the Attachments button)
+
|
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.
+
|
Try using the "group-starting-with" function
+
|
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
+
|
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"
+
|
and the third iteration is even better .....
+
|
|
