| that |
| Advanced Member |
|
| AT |
|
|
| None Specified |
|
| Friday, June 16, 2006 |
| Wednesday, March 19, 2025 3:45:54 PM |
500
[2.74% of all post / 0.07 posts per day] |
|
I cannot identify anything in your image, but let's imagine that your SQL queries produce a string each. In that case, you could create a variable component and use "duplicate input" to create an input for the result each SQL statement. To get only the first value, use the "first-items" function on the output of the variable component. That should do something very similar to the COALESCE function.
|
RobPastoor wrote:As far as I know, I only have one record/line in my MS Excel target file for each record/line that I want to map from my source file.
It only depends on what you connect to the target "Rows" node.
The most important basic rule of MapForce is: a connection will create one target item for each source item. So if you connect the output of the tokenize function to target "Rows", you will get one row per token.
RobPastoor wrote:I don't see how I can use an option such as maxOccures="Unbounded" in MS Excel, such as with an XSD/XML target file.
The "Rows" node in an Excel component is always unbounded.
RobPastoor wrote:Or can you, if it's not too much to ask, create a simple mapping that includes this?
I did a quick mapping with CSV instead of Excel, and without multiplying the position.
|
You need a tokenize function on your related articles column to get the correct number of items that you can map to output rows.
For the position number, the "position" function looks promising (on the output of "tokenize"), you just have to multiply its output by 10.
|
Without knowing your schema, this can be because the default version of JSON Schema has changed in that release, or that release had a bug, or that release fixed a bug.
Release 2021 is over 4 years old - what does the current version do?
|
Since MapForce does not use that metadata field for anything, it is very unlikely to be the actual reason for your problem. Do you get any error messages or just no data?
XLSX files are actually ZIP files, so there are likely more differences inside. If you send such a non-working XLSX file to Altova Support, I am sure they can figure out why MapForce does not like it.
|
You originally said "I expect a combination of 1 FeatureCode, 1 FeatureName and 1 UnitCode", which is what you are getting now.
How do you define "do not belong together"? These combinations of FeatureCode and UnitCode actually seem to appear in your input file.
|
Looks like you are missing a Join component to join corresponding features and units together.
|
The larger your window, the less you have to scroll.
If your mapping is too large and you have to scroll a lot:
* Extract logical parts of your mapping to user-defined functions.
* Get a big screen (30" 4K or bigger) - working with big diagrams of any kind on a small screen is a productivity killer.
* Zoom out to see more of your mapping.
* Temporarily move components closer together if you have to connect multiple nodes between them.
|
dnieuwkamp wrote:Is there a button or hotkey to Expand or Collapse all the fields within a component?
The same as in all tree controls on Windows: "*" on the keypad expands descendants of the currently selected node recursively. In addition, MapForce supports "/" on the keypad to collapse recursively.
|
RobPastoor wrote:
The unbounded elements should be concatenated, separated by a slash.
How can I solve this?
Insert a string-join component in the right place.
|
|
