You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: modules/ROOT/pages/dataweave-examples.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2095,7 +2095,7 @@ See more XML reader and writer properties on xref:dataweave-formats.adoc#xml[Dat
2095
2095
2096
2096
== Configure CSV Reader
2097
2097
2098
-
DataWeave supports CSV inputs and outputs, by configuring the reader and writer properties, you can adapt it to different conventions regarding separations, line breaks, etc. Other formats also allow for this kind of configuration. See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation] for how to do this on the UI, or look at the xref:dataweave-xml-reference.adoc#reader-configuration[DataWeave XML Reference] for the required XML syntax. You can also see a full reference of the reader properties available with CSV format on xref:dataweave-formats.adoc#csv[DataWeave formats].
2098
+
DataWeave supports CSV inputs and outputs, by configuring the reader and writer properties, you can adapt it to different conventions regarding separations, line breaks, etc. Other formats also allow for this kind of configuration. See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation] for how to do this on the UI, or look at the xref:dataweave-xml-reference.adoc#reader-configuration[DataWeave XML Reference] for the required XML syntax. You can also see a full reference of the reader properties available with CSV format on xref:dataweave-formats.adoc#csv[DataWeave formats].
2099
2099
2100
2100
Reader properties are set as part of the XML `dw:transform-message` component, whilst writer properties are specified in the DataWeave code itself, as part of the output directive. You can see a full reference to the writer properties available with CSV format on xref:dataweave-formats.adoc#writer-properties[DataWeave formats].
2101
2101
@@ -2948,7 +2948,7 @@ Based on a mapping definition, stored for instance in a DB table, you can dynami
2948
2948
2949
2949
2950
2950
[NOTE]
2951
-
Note that for this example to work, on the payload input you must set the reader configuration so that the 'nullValueOn' attribute is "empty". See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
2951
+
Note that for this example to work, on the payload input you must set the reader configuration so that the 'nullValueOn' attribute is "empty". See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
Copy file name to clipboardExpand all lines: modules/ROOT/pages/dataweave-flat-file-schemas.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,19 +7,19 @@ endif::[]
7
7
8
8
include::partial$eol-warning.adoc[]
9
9
10
-
DataWeave enables you to process several different xref:dataweave-formats.adoc[types of data]. For most of these types, you can import a schema that describes the input structure in order to have access to valuable metadata at design time. See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
10
+
DataWeave enables you to process several different xref:dataweave-formats.adoc[types of data]. For most of these types, you can import a schema that describes the input structure in order to have access to valuable metadata at design time. See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
11
11
12
12
DataWeave uses a YAML format called *FFD (for Flat File Definition)* to represent flat file schemas. The FFD format is very flexible to support a range of use cases, but is based around the concepts of *elements*, *composites*, *segments*, *groups* and *structures*.
13
13
14
14
15
15
Schemas must be written in Flat File Schema Language, with a *.ffs* extension. This language is very similar to EDI Schema Language (ESL), which is also accepted by Anypoint Studio.
16
16
17
-
On DataWeave, you can bind your input or your output to a flat file schema through a property. See xref:6@studio::transform-message-component-concept-studio.adoc[About Transform Message Component] for instructions on how to do this through the Studio UI. If you want to do this through code, see xref:dataweave-formats.adoc#flat-file[DataWeave formats] for more information, and keep in mind that the way these properties are set depends on if you're defining the input or the output.
17
+
On DataWeave, you can bind your input or your output to a flat file schema through a property. See xref:6.x@studio::transform-message-component-concept-studio.adoc[About Transform Message Component] for instructions on how to do this through the Studio UI. If you want to do this through code, see xref:dataweave-formats.adoc#flat-file[DataWeave formats] for more information, and keep in mind that the way these properties are set depends on if you're defining the input or the output.
18
18
19
19
20
20
[TIP]
21
21
====
22
-
If you intend to use a fixed-width format, you can set up your structure directly through an editor in the UI of the Transform Message component, that makes this a lot easier, just select the `Fixed Width` type. See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
22
+
If you intend to use a fixed-width format, you can set up your structure directly through an editor in the UI of the Transform Message component, that makes this a lot easier, just select the `Fixed Width` type. See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
323
+
See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
324
324
325
325
326
326
== XML
@@ -396,7 +396,7 @@ Or via the UI of the Transform Message component:
396
396
397
397
image::dataweave-formats-6e5e4.png[]
398
398
399
-
See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
399
+
See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
400
400
401
401
402
402
=== Writer Properties
@@ -465,7 +465,7 @@ In the Transform Message component, you can define a XML type through the follow
465
465
* By pointing to a schema file
466
466
467
467
[TIP]
468
-
See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
468
+
See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
469
469
470
470
=== Custom Types
471
471
@@ -546,7 +546,7 @@ In the Transform Message component, you can define a JSON type through the follo
546
546
* By pointing to a schema file
547
547
548
548
[TIP]
549
-
See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
549
+
See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
550
550
551
551
552
552
@@ -594,7 +594,7 @@ These properties can be either set via the XML of your Mule project:
594
594
595
595
Or via the UI of the Transform Message component
596
596
597
-
See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
597
+
See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
598
598
599
599
[NOTE]
600
600
Schemas with type `Binary` or `Packed` don't allow for line breaks to be detected, so setting `recordParsing` to "lenient"` will only allow long records to be handled, but not short ones. These schemas also currently only work with certain single-byte character encodings (so not with UTF-8 or any multibyte format).
@@ -641,7 +641,7 @@ In the Transform Message component, you can define a Flat File type through the
641
641
* By pointing to a schema file
642
642
643
643
[TIP]
644
-
See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
644
+
See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
645
645
646
646
647
647
@@ -690,7 +690,7 @@ These properties can be either set via the XML of your Mule project:
690
690
691
691
Or via the UI of the Transform Message component
692
692
693
-
See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
693
+
See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
694
694
695
695
=== Writer Properties
696
696
@@ -737,7 +737,7 @@ In the Transform Message component, you can define a Fixed Width type through th
737
737
image::dataweave-formats-27b3c.png[]
738
738
739
739
[TIP]
740
-
See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
740
+
See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
741
741
742
742
743
743
@@ -851,7 +851,7 @@ These properties can be either set via the XML of your Mule project:
851
851
852
852
Or via the UI of the Transform Message component
853
853
854
-
See xref:6@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
854
+
See xref:6.x@studio::input-output-structure-transformation-studio-task.adoc[To Define Input and Output Structure of a Transformation].
855
855
856
856
[NOTE]
857
857
Schemas with type `Binary` or `Packed` don't allow for line breaks to be detected, so setting `recordParsing` to "lenient"` will only allow long records to be handled, but not short ones. These schemas also currently only work with certain single-byte character encodings (so not with UTF-8 or any multibyte format).
@@ -904,7 +904,7 @@ See xref:dataweave-flat-file-schemas.adoc[Flat File Schemas] for more detailed i
The DataWeave language is a powerful template engine that allows you to transform data to and from any kind of format (XML, CSV, JSON, Pojos, Maps, etc). In Anypoint Studio, this language can be used in:
11
11
12
-
* The *Transform Message Component*, described in xref:6@studio::transform-message-component-concept-studio.adoc[About Transform Message Component]
12
+
* The *Transform Message Component*, described in xref:6.x@studio::transform-message-component-concept-studio.adoc[About Transform Message Component]
13
13
* Any Mule component that accepts Mule Expression Language, through xref:3.8@mule-runtime::mel-dataweave-functions.adoc[MEL DataWeave Functions]
14
14
15
15
@@ -1277,6 +1277,6 @@ Likewise, whenever you transform from XML to JSON, make sure the resulting outpu
Copy file name to clipboardExpand all lines: modules/ROOT/pages/dataweave-migrator.adoc
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@ endif::[]
7
7
8
8
include::partial$eol-warning.adoc[]
9
9
10
-
If you have projects that are built with the deprecated xref:6@studio::datamapper-user-guide-and-reference.adoc[DataMapper], a migration tool is now included in Studio, which assists in converting a DataMapper map to DataWeave. This tool doesn't replace the original DataMapper in your flow, it creates a new equivalent DataWeave component next to it. The old DataMapper component is left in its place so that you can compare both as they sit next to each other on your flow, but you must then delete it for the flow to be executable.
10
+
If you have projects that are built with the deprecated xref:6.x@studio::datamapper-user-guide-and-reference.adoc[DataMapper], a migration tool is now included in Studio, which assists in converting a DataMapper map to DataWeave. This tool doesn't replace the original DataMapper in your flow, it creates a new equivalent DataWeave component next to it. The old DataMapper component is left in its place so that you can compare both as they sit next to each other on your flow, but you must then delete it for the flow to be executable.
Use the xref:6@studio::transform-message-component-concept-studio.adoc[About Transform Message Component] to create the actual mapping between the input and output fields. Simply click and drag a field in the input side to a field in the output side. The most obvious task is to match similarly named fields together, thus helping to validate the output data:
168
+
Use the xref:6.x@studio::transform-message-component-concept-studio.adoc[About Transform Message Component] to create the actual mapping between the input and output fields. Simply click and drag a field in the input side to a field in the output side. The most obvious task is to match similarly named fields together, thus helping to validate the output data:
169
169
170
170
** `address` and `address1`
171
171
** `city` and `city`
@@ -528,7 +528,7 @@ If you open the *Preview* section, you can see what this transform would output,
528
528
== See Also
529
529
530
530
* More advanced examples in xref:dataweave-examples.adoc[DataWeave Examples]
Copy file name to clipboardExpand all lines: modules/ROOT/pages/dataweave-reference-documentation.adoc
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -305,7 +305,7 @@ Valid types are:
305
305
306
306
When defining an input of type CSV, there are a few optional parameters you can add to the input directive to customize how the data is parsed. These are not defined in the DataWeave script but on the Mule XML code, in the Transform Message XML element.
307
307
308
-
In Anypoint Studio there are two ways to achieve this. You can either manually add the attributes to the project's XML, or do it through the graphical interface, by selecting the element from the tree view in the input section and clicking the gear icon. See xref:5@studio::using-dataweave-in-studio.adoc#parsing-csv-inputs[Using DataWeave in Studio] for more details.
308
+
In Anypoint Studio there are two ways to achieve this. You can either manually add the attributes to the project's XML, or do it through the graphical interface, by selecting the element from the tree view in the input section and clicking the gear icon. See xref:5.x@studio::using-dataweave-in-studio.adoc#parsing-csv-inputs[Using DataWeave in Studio] for more details.
Your DataWeave code can call any function you define as a global xref:3.7@mule-runtime::mule-expression-language-mel.adoc[Mule Expression Language (MEL)] function, as long as it is correctly defined in the Mule Project where your Transform Message element sits.
3478
3478
3479
-
Refer to xref:5@studio::using-dataweave-in-studio.adoc#calling-global-mel-functions-from-dataweave-code[Using DataWeave in Studio].
3479
+
Refer to xref:5.x@studio::using-dataweave-in-studio.adoc#calling-global-mel-functions-from-dataweave-code[Using DataWeave in Studio].
In Anypoint Studio, you can define several more values, like separators, quote characters and escape characters. See xref:5@studio::using-dataweave-in-studio.adoc#configuring-the-csv-reader[Using DataWeave in Studio].
4062
+
In Anypoint Studio, you can define several more values, like separators, quote characters and escape characters. See xref:5.x@studio::using-dataweave-in-studio.adoc#configuring-the-csv-reader[Using DataWeave in Studio].
4063
4063
4064
4064
== Functions and Lambdas
4065
4065
@@ -4220,6 +4220,6 @@ You can reference any *Property* (System or Spring) that exists in the server wh
4220
4220
4221
4221
== See Also
4222
4222
4223
-
* xref:5@studio::using-dataweave-in-studio.adoc[Using DataWeave in Studio]
4223
+
* xref:5.x@studio::using-dataweave-in-studio.adoc[Using DataWeave in Studio]
0 commit comments