underpar |
Member |
|
everywhere |
|
|
None Specified |
|
Wednesday, December 11, 2013 |
Thursday, August 24, 2017 4:32:33 PM |
18 [0.10% of all post / 0.00 posts per day] |
|
It is not possible to add libraries via relative paths.
Altova Support Engineer
|
I assume by "database mapping" you mean that you are mapping contents of a database "source" table to a database "target" table. If this is the case, then this message likely has to to with the fact that you have not connected anything to the "table connector" of the "target" table i.e. have not connected a field in the source table to the "table connector" of the "target" table or have not connected the "table connector" of the "source" table to the "table connector" of the "target" table.
By "table connector" of the "target table" I mean the connector to the left of the table name in the target database component of your mapping. The Messages window in Mapforce should be showing TWO warnings i.e.
New Design1: Mapping validation successful - 0 error(s), 1 warning(s) Table2 has no input connection and will be generated only once. You can try to connect Table1 with Table2 to resolve.
New Design1: Execution successful - 0 error(s), 1 warning(s) One or several additional values were skipped. The value "a" was mapped. First skipped value(s): "b", "c".
The first warning points to the cause e.g. "Table2" (the target table) has no input connection (i.e. nothing has been mapped to the table connector of the target database table.) as well as a proposed solution i.e. "You can try to connect Table1 with Table2 to resolve."
Compare the two screenshots below.
Altova Support Engineer
|
In general we would suggest using the Mapforce built-in engine (Mapforce Server) to execute mappings (as opposed to generating code) because the built-in engine contains various performance optimizations as well as other benefits e,g, supporting true streaming of large files.
Altova Support Engineer
|
With respect to validation the schema for schemas is hardcoded in the software.
Altova Support Engineer
|
Hi,
See attached mapping solution which uses "group-starting-with".
Altova Support Engineer
|
Note that the following will work (META tag is closed with forward slash at end of tag) and quotes are prepended with a backslash:
var str = "<!DOCTYPE html><html><head><META http-equiv=\"Content-Type\" content=\"text/html; charset=utf-8\"/><title>Some Title</title></head><body></body></html>"
Application.Documents.NewFileFromText(str , "html");
Altova Support Engineer
|
This would appear to be a bug and has been logged in the internal bug database
The bug entry number is TTP# 52761
Application.Documents.NewFileFromText method returns an error if the first parameter is not well formed xml (even for non xml file types)
As soon as this issue has been addressed it will appear on our release notes page:
Altova Support Engineer
|
Hi,
this behaviour should be fixed in an upcoming release i.e. so that when the schema reloads the "compute-when" does not revert to its initial state.
Altova Support Engineer
|
Hi,
sorry about the multiple notifications, we will reduce these to a single announcement per MissionKit.
Altova Support Engineer
|
Hi,
a schema for mfd files is not provided.. .
Altova Support Engineer
|
|