| K101 |
| Advanced Member |
|
|
|
|
| None Specified |
|
| Friday, February 27, 2009 |
| Friday, August 7, 2020 12:10:25 PM |
395
[2.25% of all post / 0.09 posts per day] |
|
What content-type is MapForce sending now? Which WSDL version (1.1 or 2.0) are you using? Which SOAP version is the request (1.1 or 1.2)? Can you attach the WSDL?
Technical Support
Altova GmbH
|
You need to use grouping, an intermediate variable, and duplicate the E1EDL24 item in the variable.
Technical Support
Altova GmbH
|
Regarding the conversion of xsd:string to bit, that appears to be a genuine problem. I recommend you report this directly to Altova Support.
Regarding the relationship, note that XMLSpy will create relationships between the tables when the schema has relationships defined in the form of identity constraints (see “Creating DB tables with relationships”). So, first add these to your schema, then try converting again.
Technical Support
Altova GmbH
|
Because your input component is processing multiple files (*.csv), but you have nothing coming out of that input component's File item, you're grouping all the rows from all the input files.
If you want, per input file to create one or more output files, you have to connect the File item from the input component to the output component's File item one way or another.
Technical Support
Altova GmbH
|
Well, that's a lot of ground to cover.
2800 "fields": if your XML structure is simply a repeating element with 2800 fields (attribute or element), then it's fairly straightforward to convert it to a database table. You will likely run into limitations of the number of columns a table can have. Normally, SQL Server has a hard limit of 1,024 columns, but there are apparently ways to work around that.
You can use XMLSpy to convert your XML schema to a database structure, but you will likely need to edit it further using DatabaseSpy to actually work with SQL Server for at least this reason.
If your schema is more complex than can be simply represented in a single table's row/column structure, XMLSpy may need to generate multiple, related tables to represent the structure.
XMLSpy can export your XML data files directly to a database, but this is intended more as a one-time operation, rather than something you can automate. For that, you're better off using MapForce to create a mapping between your XML schema (representing your XML data files) and the database structure you converted your schema to using XMLSpy.
The mapping will be set up to process all *.xml files (for example) in your input folder.
For more complete automation, you'll need to use MapForce Server to run your mapping from the command line or via API.
More complex workflow automation requirements (scheduling, triggering, etc.) may necessitate the use of FlowForce Server.
Technical Support
Altova GmbH
|
You can certainly create a mapping from CSV to a web service call, if that's what you mean.
Technical Support
Altova GmbH
|
This is something for future consideration.
Technical Support
Altova GmbH
|
It appears that XMLSpy presently supports only regular WebSocket ws connections to RaptorXML Server, rather than WebSocket Secure wss connections, so this will have to be taken under future consideration.
Technical Support
Altova GmbH
|
There are some known issues involving incoming messages from Unix-based systems with LF line endings. Some fixes were included in v2020r2, and more are coming in Service Pack 1 for that version.
I recommend you contact Altova Support directly with more details about your particular case for more definitive information.
Technical Support
Altova GmbH
|
What's your target output format? PDF? In that case it seems to me it might be possible using the page-number-citation-last element, but I can't get that to work with Apache FOP even by crafting raw FO.
Technical Support
Altova GmbH
|
|
