XML Generator
- Kalpana Malladi
- Aparna Tayi (Unlicensed)
- John Brinckwirth
On this Page
Snap type: | Read | |||||||
---|---|---|---|---|---|---|---|---|
Description: | This Snap generates a new XML document for the next Snap in the pipeline. The Snap will pass-through the input data if an input view is provided. The output of the Snap will provide an XML attribute in the document which provides the serialized XML content as a string.
| |||||||
Prerequisites: | [None] | |||||||
Support and limitations: | Works in Ultra Tasks. | |||||||
Account: | Accounts are not used with this Snap. | |||||||
Views: |
| |||||||
Settings | ||||||||
Label | Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline. | |||||||
Inbound schema | XML schema definition of the incoming data. | |||||||
Schema XPath | The path for the schema object in the provided schema file, which must be used for validating the XML data. This is required if the schema object is nested within a wrapper object or within an object further in the schema file. See example Validating XML Data Using the Schema XPath for more information on using the Schema XPath field. | |||||||
XML root element | Root element for the XML generation. | |||||||
Validate XML | Required. Appears when you specify an XSD schema definition in the Inbound schema field. Select this checkbox to validate the incoming data against the specified XSD schema definition. If you enter an Inbound schema, then you must select Validate XML and Match data types properties to derive the output as per the defined schema. Default Value: Deselected | |||||||
Escape special characters | Select this checkbox to escape XML special characters in XML template variable values when you insert the values into the Apache Velocity template. For example, the Snap replaces < with &It;. The special characters that the Snap escapes are:
XML Generator normalizes all attributes to use double quotes for the delimiters, even if the source content uses single quotes. Therefore, if there are double quotes that appear inside the attributes, then they have to be escaped. Learn more: XML Generator#HandlingSpecialCharacters. Default value: Not selected We recommend that you select this checkbox unless your variable values contain XML Markup or the contents are already escaped. | |||||||
Default value for substitution | This value will be used for substitution for the leaf elements which are not objects and/or not enclosed in an array. If nothing is specified and Use default value for substitution is selected, an empty string will be used for substitution. | |||||||
Use default value for substitution | If you select this check box, the value provided for the Default value for substitution is used for substitution if the elements do not exist in the incoming documents. Otherwise, the elements for which the incoming documents do not have any values will be deleted from the XML. | |||||||
Namespace Context | Namespace context for schema element. | |||||||
Prefix | Prefix of schema element in the provided schema file. | |||||||
Namespace URI | Namespace of schema element in the provided schema file. | |||||||
Edit XML | Required. This property lets you edit the XML contents. The elements to be generated in the output must be specified in the XML template. If your output does not display the required elements, click Edit XML and specify the applicable elements in the Generate Template tab. You can use the /wiki/spaces/AP/pages/1438085 template to pass dynamic values from upstream Snaps. Elements specified in the schema document in the Inbound schema field do not affect the output. | |||||||
Snap Execution | Select one of the three modes in which the Snap executes. Available options are:
|
Handling Special Characters
The following are the basic rules when the special characters are to be escaped:
If the special characters are inside the element text, then they are not to be escaped.
If the special characters are inside the attribute values that are delimited by single or double quotes, then they are to be escaped.
If the special characters and the delimiter being used for that attribute are the same, then they are to be escaped.
The following table lists a few examples of how to escape special characters:
Example | Attribute/Element in XML | Description |
---|---|---|
He said "OK" | attributeName="He said "OK"" | The double quotes must be escaped. |
He said "OK" | attributeName='He said "OK"' | The double quotes need not be escaped as they are contained within a single-quoted attribute. |
She said "You're right" | attributeName="She said "You're right"" | The ' (apostrophe) in You’re need not be escaped as it is contained within double quotes. |
She said "You're right" | attributeName='She said "You're right"' | The double quotes need not be escaped as they are contained within a single-quoted attribute. However, you must escape the apostrophe in You’re. |
She said "You're right" | attributeName="She said "You're right"" | To escape all the data. |
Smith&Sons | attributeName="Smith&Sons" | The & must always be escaped within attribute data. |
a>b a<b | attributeName="a>b" attributeName="a<b" | It is good practice to escape > or < characters, though not mandatory if they are used in an attribute. |
if (age < 5) if (age > 5) if (age > 3 && age < 8) | <MyElement>if (age < 5)</MyElement> <MyElement>if (age > 5)</MyElement> <MyElement>if (age > 3 && age < 8)</MyElement> | It is good practice to escape >, <, or & characters if they are used within an element though not mandatory. |
She said "You're right" | <MyElement>She said "You're right"</MyElement> | The single and double quotes need not be escaped if they are within an Element |
Troubleshooting
XML Formatter and XML Generator Output Differs for the Same XSD File Input
The XML Formatter and XML Generator Snaps work differently for an XSD file as the input document. To generate the same output from both the Snaps, append the following to the required schema in the Target path property of the preceding Mapper Snap:
- XML Formatter:
.$
- XML Generator:
.value
Examples
XML Generation via XSD
The first example depicts a simple pipeline to generate order data XML directly with the XML Generator Snap.
We provide the sample XSD as defined below:
<?xml version="1.0" encoding="UTF-8" ?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:element name="shiporder"> <xs:complexType> <xs:sequence> <xs:element name="orderperson" type="xs:string"/> <xs:element name="shipto"> <xs:complexType> <xs:sequence> <xs:element name="name" type="xs:string"/> <xs:element name="address" type="xs:string"/> <xs:element name="city" type="xs:string"/> <xs:element name="country" type="xs:string"/> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="item" maxOccurs="unbounded"> <xs:complexType> <xs:sequence> <xs:element name="title" type="xs:string"/> <xs:element name="note" type="xs:string" minOccurs="0"/> <xs:element name="quantity" type="xs:positiveInteger"/> <xs:element name="price" type="xs:decimal"/> </xs:sequence> </xs:complexType> </xs:element> </xs:sequence> <xs:attribute name="orderid" type="xs:string" use="required"/> </xs:complexType> </xs:element> </xs:schema>
Originated from: http://www.w3schools.com/schema/schema_example.asp
We then suggest the XML root element, which returns {}shiporder.
Finally we click on Edit XML, which will automatically trigger the XML template generation based off the XSD, see below.
Now we could replace the variables with our own values to generate the XML on the output view or move on to the next example.
*The execution of the Snap above will create an XML attribute on the output view which provides the serialized XML content as a string.
Mapping to XML Generator via XSD
Let us use a JSON Generator to provide the input order data, such as defined below:
[ { "items" : [{ "title": "iphone6", "quantity": 1, "price": 598.00 }, { "title": "note 4", "quantity": 1, "price": 599.00 } ], "address":"some address", "city": "San Mateo", "orderId": "1234", "name": "Mr. Undecided" }, { "items" : [{ "title": "iphone6", "quantity": 1, "price": 598.00 }, { "title": "note 4", "quantity": 1, "price": 599.00 }, { "title": "lumina", "quantity": 1, "price": 0.99 } ], "address":"some address", "city": "San Mateo", "orderId": "1234", "name": "Mr. Even more Undecided" } ]
We then map the data using the Mapper Snap which has access to the XSD of the downstream XML Generator Snap of the previous example (now with an added input view).
Here we map the items to the item list on the target. Further we map the city, address, country and name to the shipTo object on the target and then finally we map the name against orderperson and orderId against @orderId on the target. The @ indicates we map against an XML attribute
Let us see the output of the XML Snap.
Here we see that each incoming order document was translated into an xml string. We include the original data from the input view, in case it is further needed downstream.
The XML Generator Snap can validate the generated content if needed using the “Validate XML” property.
Writing the Generated Content to File
Sometimes one wants to write the generated XML to a file. For that use case we provide a DocumentToBinary Snap which can take the content and convert it to binary data object, which then can be written to a file, such as using a File Writer Snap.
Above we map XML to the content field of the DocumentToBinary Snap, and set the Encode or Decode option on the DocumentToBinary Snap to NONE.
This outputs then one binary document for each order. We can then write it to a directory. (Careful, here you’d want to use the APPEND option, since you potentially would be writing two files to the same directory or you can use an expression such as Date.now() to write individual files for each incoming binary data object).
POSTing the Generated Content
In the last example we will be POSTing the generated content to some REST endpoint using the REST POST Snap.
In the screenshot below we are using the POST Snap which has the entity set as $xml. That will use the XML content that was generated by the upstream XML Generator Snap and POST it as a body to the endpoint.
You might want to set the content-type and accept header as defined below.
The POST will be executed for every document on the input view. There are a total of two documents, hence we will execute two post requests.
Validating XML Data Using the Schema XPath and Validate XML Settings
This example demonstrates how to use the Schema XPath field to successfully validate XML data.
Download the Sample Pipeline.
In this Pipeline, custom XML data is provided using the Edit XML field in the XML Generator Snap, a snapshot of which is provided here.
The Inbound schema, Schema XPath, and the schema Root element, are specified in the Snap settings. See the screenshot below. In addition, the Validate XML check box is selected to indicate that the XML data must be validated against the schema.
The file specified as the inbound schema, CustomersOrders_withXSD.xml,
is not a regular schema file (.xsd) but an XML file being used as a schema file. The contents of this file appear as follows:
In the above file, the root element of the schema is nested within the RootElm
object. Therefore, the Schema XPath field value is specified as //RootElm/*
to direct the XML Generator Snap to the schema object.
On validating the Pipeline, the Snap output appears as follows. Note the ContactName
field.
If the ContactName
field is removed from the custom XML specified in the XML editor and the Pipeline is re-validated, the Snap fails with the following error:
Note that if the Validate XML check box is deselected, the Snap does not validate the data against the schema, and an output with the missing field is generated without errors:
Similarly, if the Schema XPath value is not provided, the Snap is unable to locate the root element and fails with the following error:
This explains the scenarios in which you need to provide the schema XPath and how you can validate XML data using schema from within any XML or XSD file with the help of the Schema XPath and Validate XML properties.
Custom XML Output Generation using Inbound Schema and Root Element
This example illustrates the corrected behavior of the XML Generator Snap as of Patch transform8760, whereby the Snap does not ignore any custom XML data that is provided through its XML editor.
Download the Sample Pipeline.
Scenario 1: When used with upstream Snaps
The sample Pipeline provided here generates XML for an Add operation. The XML output should contain two integer values: intA and intB.
Using two XML Generator Snaps: Customized XML and Generated XML, the Pipeline demonstrates the differing output when custom XML is provided vs when the output is generated using upstream data. Both Snaps are provided the same schema info.
In the Customized XML Snap, custom XML data is provided using the Edit XML field in the Snap Settings as follows:
Here, the values of intA
and intB
are 0
and 1
respectively.
The Generated XML Snap contains the XML that is generated through the Generate Template button in the XML editor:
In this case, the values of intA
and intB
are dynamically assigned when the Snap executes.
Both Snaps are fed an input document that specifies intA=2,
and intB=3.
Old behavior:
The Customized XML Snap had the same output as the Generated XML Snap and ignored the custom XML data in the editor:
Current behavior:
The two Snaps have different outputs. The output of the Customized XML Snap is based on the XML provided by the user:
The output of the Generated XML Snap is based on upstream data:
Scenario 2: When used as a standalone Snap
The sample Pipeline provided below generates XML for an Add operation.
Custom XML is provided using the Edit XML field, as follows:
Old behavior:
Pipeline execution would result in a Premature end of file
error:
Current behavior:
Pipeline execution is successful and custom XML output is generated:
This example illustrates how you can generate custom XML output through the XML Generator Snap.
Downloads
Important steps to successfully reuse Pipelines
- Download and import the pipeline into the SnapLogic application.
- Configure Snap accounts as applicable.
- Provide pipeline parameters as applicable.
File | Modified | |
---|---|---|
Apr 24, 2020 by Ritu Sachdeva | ||
Apr 24, 2020 by Ritu Sachdeva |
Release | Snap Pack Version | Date | Type | Updates | ||||||
---|---|---|---|---|---|---|---|---|---|---|
August 2024 | 438patches28073 | Latest | Fixed an issue with the JSON Generator and XML Generator Snaps that caused unexpected output displaying '__at__' and '__h__' instead of '@' and '-' respectively because the Snap could not update them to their original values after the Velocity library upgrade. | |||||||
August 2024 | 438patches27959 | Latest | Fixed an issue with the Sort where the Snap could not sort files larger than 52 MB. This fix applies to Join Snap also. | |||||||
August 2024 | main27765 | Stable | Upgraded the org.json.json library from v20090211 to v20240303, which is fully backward compatible. | |||||||
May 2024 | 437patches26643 | Latest |
| |||||||
May 2024 | 437patches26453 | Latest |
| |||||||
May 2024 | main26341 | Stable |
| |||||||
February 2024 | 436patches25564 | Latest | Fixed an issue with the JSON Formatter Snap that generated incorrect schema. | |||||||
February 2024 | 436patches25292 | Latest | Fixed an If the input documents are unsorted and GROUP-BY fields are used, you must use the Sort Snap upstream of the Aggregate Snap to presort the input document stream and set the Sorted stream field Ascending or Descending to prevent the Learn more about presorting unsorted input documents to be processed by the Aggregate Snap. | |||||||
February 2024 | main25112 | Stable | Updated and certified against the current SnapLogic Platform release. | |||||||
November 2023 | 435patches24802 | Latest | Fixed an issue with the Excel Parser Snap that caused a null pointer exception when the input data was an Excel file that did not contain a StylesTable . | |||||||
November 2023 | 435patches24481 | Latest | Fixed an issue with the Aggregate Snap where the Snap was unable to produce the desired number of output documents when the input was unsorted and the GROUP-BY fields field set was used. | |||||||
November 2023 | 435patches24094 | Latest | Fixed a deserialization issue for a unique function in the Aggregate Snap. | |||||||
November 2023 | main23721 | Stable | Updated and certified against the current SnapLogic Platform release. | |||||||
August 2023 | 434patches23076 | Latest | Fixed an issue with the Binary to Document Snap where an empty input document with Ignore Empty Stream selected caused the Snap to stop executing. | |||||||
August 2023 | 434patches23034 | Latest | ||||||||
August 2023 | 434patches22705 | Latest | Fixed an issue with the JSON Splitter Snap that caused the pipeline to terminate with excessive memory usage on the Snaplex node after the 4.33 GA upgrade. The Snap now consumes less memory. | |||||||
August 2023 | main22460 | Stable | Updated and certified against the current SnapLogic Platform release. | |||||||
May 2023 | 433patches22431 | Latest |
| |||||||
May 2023 | 433patches21779 | Latest | The Decrypt Field and Encrypt Field Snaps now support CTR (Counter mode) for the AES (Advanced Encryption Standard) block cipher algorithm. | |||||||
May 2023 | 433patches21586 | Latest | The Decrypt Field Snap now supports the decryption of various encrypted fields on providing a valid decryption key. | |||||||
May 2023 | 433patches21461 | Latest | The following Transform Snaps include new fields to improve memory management: Aggregate, Group By Fields, Group By N, Join, Sort, Unique. | |||||||
May 2023 | 433patches21336 | Latest | Fixed an issue with the AutoPrep Snap where dates could potentially be rendered in a currency format because currency format options were displayed for the DOB column. | |||||||
May 2023 | 433patches21196 | Latest | Enhanced the In-Memory Lookup Snap with the following new fields to improve memory management and help reduce the possibility of out-of-memory failures:
These new fields replace the Maximum memory % field. | |||||||
May 2023 | main21015 | Stable | Upgraded with the latest SnapLogic Platform release. | |||||||
February 2023 | 432patches20535 | Latest | Fixed an issue with the Encrypt Field Snap, where the Snap failed to support an RSA public key to encrypt a message or field. Now the Snap supports the RSA public key to encrypt the message. | |||||||
February 2023 | 432patches20446 | Latest | The Join Snap is enhanced with the following:
| |||||||
February 2023 | 432patches20250 | Latest |
| |||||||
February 2023 | 432patches20151 | Stable/Latest | Fixed an issue that occurred with the JSON Splitter Snap when used in an Ultra pipeline. The request was acknowledged before it was processed by the downstream Snaps, which caused a 400 Bad Request response. | |||||||
February 2023 | 432patches20062 | Stable/Latest | Fixed the behavior of the JSON Splitter Snap for some use cases where its behavior was not backward compatible with the 4.31 GA version. These cases involved certain uses of either the Include scalar parents feature or the Include Paths feature. | |||||||
February 2023 | 432patches19974 | Stable/Latest | Fixed the Review your pipelines where this error occurred to check your assumptions about the input to the JSON Splitter and whether the value referenced by the JSON Path to Split field will always be a list. If the input is provided by an XML-based or SOAP-based Snap like the Workday or NetSuite Snaps, a result set or child collection that’s an array when there's more than one result or child will be an object when there's only one result or child. In these cases, we recommend using a Mapper Snap and the | |||||||
February 2023 | 432patches19918 | Stable/Latest |
| |||||||
February 2023 | main19844 | Stable | Upgraded with the latest SnapLogic Platform release. | |||||||
November 2022 | 431patches19441 | Stable | The Encrypt Field Snap supports decryption of encrypted output in Snowflake Snaps. | |||||||
November 2022 | 431patches19385 | Latest | The Transform Join Snap now doesn’t fail with the | |||||||
November 2022 | 431patches19359 | Latest | The JSON Splitter Snap includes memory improvements and a new Exclude List from Output Documents checkbox. This checkbox enables you to prevent the list that is split from getting included in output documents, and this also improves memory usage. | |||||||
November 2022 | main18944 | Stable |
| |||||||
October 2022 | 430patches18800 | Latest | The Sort and Join Snaps now have improved memory management, allowing used memory to be released when the Snap stops processing. | |||||||
October 2022 | 430patches18610 | Latest | The CSV Formatter and CSV Parser Snaps now support shorter values of Unicode characters. | |||||||
October 2022 | 430patches18454 | Latest |
| |||||||
The CSV Parser Snap now parses data with empty values in the columns when using a multi-character delimiter. | ||||||||||
September 2022 | 430patches18119 | Latest | The Transcoder Snap used in a low-latency feed Ultra Pipeline now acknowledges the requests correctly. | |||||||
September 2022 | 430patches17802 | Latest | The Avro Parser Snap now displays the decimal number correctly in the output view if the column’s logical type is defined as a decimal. | |||||||
September 2022 | 430patches17737 | Stable/Latest | AutoPrep now enables you to handle empty or null values. | |||||||
September 2022 | 430patches17643 | Latest | The CSV Parser and CSV Formatter Snaps now support either \ or \\ for a single backslash delimiter which were failing earlier. | |||||||
September 2022 | 430patches17589 | Latest | The CSV Formatter Snap does not hang when running in specific situations involving multibyte characters in a long field. If you notice the CSV Formatter Snap is hung, we recommend that you update to the 430patches17589 version and restart your Snaplex. | |||||||
August 2022 | main17386 | Stable |
| |||||||
4.29 Patch | 429patches16990 | Latest |
| |||||||
4.29 Patch | 429patches16923 | Latest |
| |||||||
4.29 Patch | 429patches16521 | Latest |
| |||||||
4.29 Patch | 429patches16026 | Latest | Enhanced the Excel Parser Snap with the Custom Locale dropdown list that allows you to select a user-defined locale to format numbers as per the selected locale. | |||||||
4.29 | main15993 | Stable |
| |||||||
4.28 patch | 428patches14370 | Latest | Fixed an issue with the XML Generator Snap, where the Snap failed with an invalid UTF-8 sequence error when running on the Windows Snaplex. | |||||||
4.28 | main14627 | Stable | Upgraded with the latest SnapLogic Platform release. | |||||||
4.27 Patch | 427patches12966 | Latest | Enhanced the Avro Formatter Snap to display meaningful error message while processing invalid and null values from the input. | |||||||
4.27 | main12989 | Stable and Latest | Fixed an issue in the Group by Fields Snap that caused the Snap to abort with an error when executed with zero input documents. | |||||||
4.27 | main12833 | Stable |
| |||||||
4.26 Patch | 426patches12086 | Latest | Fixed an issue with the Join Snap, where it exhausted the memory while buffering millions of objects. | |||||||
4.26 Patch | 426patches11780 | Latest | Fixed an issue in the XML Formatter Snap, where the Map input to first repeating element in XSD checkbox is selected, while no XSD is specified for mapping the input. | |||||||
4.26 Patch | 426patches11725 | Latest | Fixed an issue with the Join Snap where the upstream document flow of the right view is blocked by the left view, which hung the Join Snap. | |||||||
4.26 | main11181 | Stable |
| |||||||
4.25 Patch | 425patches10663 | Latest | Fixed an issue in the CSV Formatter Snap, where even if the Ignore empty stream checkbox is not enabled, the Snap did not produce an empty binary stream output in case there is no input document. | |||||||
4.25 Patch | 425patches10152 | Latest |
| |||||||
4.25 Patch | 425patches9815 | Latest | Fixed a | |||||||
4.25 Patch | 425patches9749 | Latest | Enhanced XML Parser Snap to recognize input headers when defining inbound schema. | |||||||
4.25 Patch | 425patches9638 | - | Latest | Reverts the Join Snap to the 4.24 release behavior. This is in response to an issue encountered in the Join Snap in the 4.25 release version (main9554), which can result in incorrect outputs from all Join Types. 425patches9638 is the default version for both stable and latest Transform Snap Pack versions for orgs that are on the 4.25 release version. No action is required by customers to receive this update and no impact is anticipated. | ||||||
4.25 | main9554 | Stable | Enhanced the Group By N Snap with the following settings:
| |||||||
4.24 Patch | 424patches8938 | Latest |
| |||||||
4.24 | main8556 | Stable | Upgraded with the latest SnapLogic Platform release. | |||||||
4.23 Patch | 423patches7958 | Latest | Fixes an issue in the JSON Splitter Snap by logging an error when the matcher does not find a pattern. | |||||||
4.23 Patch | 423patches7898 | Latest |
| |||||||
4.23 Patch | 423patches7792 | Latest | Fixes an issue in the XML Formatter Snap when it fails to convert input JSON data, with JSON property having a special character as its prefix, to XML format by sorting the elements. | |||||||
4.23 Patch | 423patches7753 | Latest | Fixes an issue with the JSON Splitter Snap's behavior in Ultra Pipelines that prevents processed requests to be acknowledged and removed from the FeedMaster queue, resulting in retries of requests that are already processed successfully. | |||||||
4.23 | main7430 | Stable | Enhances the JSON Formatter Snap to render groups output from upstream (Group by) Snaps with one document per group and a new line per group element. You can now select the Format each document and JSON lines check boxes simultaneously. | |||||||
4.22 Patch | 422patches6395 | Latest | Fixes the JSON Splitter Snap data corruption issue by copying the data in JSON Splitter Snap before sending it to other downstream Snaps. | |||||||
4.22 Patch | 422patches6505 | Latest | Fixes the XML Generator Snap issue reflecting empty tags and extra space by removing the extra space in the XML output. | |||||||
4.22 | main6403 | Latest | Upgraded with the latest SnapLogic Platform release. | |||||||
4.21 Patch | 421patches5901 | Latest | Enhances the JSON Generator Snap to include pass-through functionality where the Snap embeds the upstream input document under the | |||||||
4.21 Patch | 421patches5848 | Latest |
| |||||||
4.21 | snapsmrc542 | - | Stable | Adds support in the Mapper Snap to display schemas with complex nesting. For example, if Snaps downstream from the | ||||||
4.20 Patch | transform8792 | - | Latest | Resolves the | ||||||
4.20 Patch | transform8788 | - | Latest | Resolves the NullPointerException in the Join Snap on Windows Snaplex instances. | ||||||
4.20 Patch | transform8760 | - | Latest |
The JSON Formatter Snap output now includes only those fields from the input file that are specified in the Content field under Settings. If your Pipelines use the JSON Formatter Snap with the JSON lines field selected, they may fail to execute correctly if the Content field mentions a specific object or field but the downstream Snap is expecting the entire data. Hence, for backward compatibility, you must review the entries in the Content field based on the desired output, as follows:
The behavior of the Snap when the JSON lines field is not selected is correct and remains unchanged. The Example: Filtering Output Data Using the JSON Formatter Snap's Content Setting further illustrates the corrected vs the old behavior.
XML Generator Snap behavior might break existing Pipelines The XML Generator Snap now gives precedence to any custom XML data that is provided over data coming from upstream Snaps, to generate the output. Existing Pipelines using the XML Generator Snap may fail in the following scenarios. Use the resolution provided to update the Snap settings based on the XML data you want to pass to downstream Snaps.
| ||||||
4.20 Patch | transform8738 | - | Latest |
| ||||||
4.20 | snapsmrc535 | - | Stable | Upgraded with the latest SnapLogic Platform release. | ||||||
4.19 Patch | transform8280 | - | Latest | Fixed an issue with the Excel Parser Snap wherein the Snap incorrectly outputs Unformatted General Number format. | ||||||
4.19 | snaprsmrc528 | - | Stable | The output of the AVG function in the Aggregate Snap now rounds up all numeric values that have more than 16 digits. | ||||||
4.18 Patch | transform8199 | - | Latest | Fixed an issue with the Excel Multi Sheet Formatter Snap wherein the Snap fails to create sheets in the expected order. | ||||||
4.18 Patch | transform7994 | - | Latest | Added a field, Round dates, to the Excel Parser Snap which enables you to round numeric excel data values to the closest second. | ||||||
4.18 Patch | transform7780 | - | Latest |
| ||||||
4.18 Patch | transform7741 | - | Latest | Fixed an issue with the Sort and Join Snaps wherein the platform removes all temp files at the end of Pipeline execution. | ||||||
4.18 Patch | transform7711 | - | Latest | Fixed an issue with the XML Parser Snap wherein a class cast exception occurs when the Snap is configured with a Splitter and Namespace Context. | ||||||
4.18 | snapsmrc523 | - | Stable |
| ||||||
4.17 Patch | Transform7431 | - | Latest | Added a new field, Ignore empty stream, to the Avro Formatter Snap that writes an empty array in the output in case of no input documents. | ||||||
4.17 Patch | Transform7417 | - | Latest | Added a new field, Format as canonical XML, to the XSLT Snap that enables canonical XML formatting. | ||||||
4.17 Patch | ALL7402 | - | Latest | Pushed automatic rebuild of the latest version of each Snap Pack to SnapLogic UAT and Elastic servers. | ||||||
4.17 | snapsmrc515 | - | Stable |
| ||||||
4.16 Patch | transform7093 | - | Latest | Fixed an issue with the XSLT Snap failure by enhancing the Saxon version. | ||||||
4.16 Patch | transform6962 | - | Latest |
| ||||||
4.16 Patch | transform6869 | - | Latest | Fixed an issue with the XML Parser Snap wherein XSD with annotations were incorrectly interpreted. | ||||||
4.16 | snapsmrc508 | - | Stable | Upgraded with the latest SnapLogic Platform release. | ||||||
4.15 Patch | transform6736 | - | Latest | Fixed an issue wherein the XML Generator Snap was unable to escape some of the special characters. | ||||||
4.15 Patch | transform6680 | - | Latest | Fixed an issue with the Excel Parser Snap wherein headers were not parsed properly and header columns were also maintained in an incorrect order. | ||||||
4.15 Patch | transform6402 | - | Latest | Fixed an issue with an object type in the Fixed Width Formatter Snap. | ||||||
4.15 Patch | transform6386 | - | Latest | Fixed an issue with the Fixed Width Parser Snap wherein Turkish characters caused incorrect parsing of data on Windows plex. | ||||||
4.15 Patch | transform6321 | - | Latest | Fixed an issue with the XML Parser Snap wherein the Snap failed to get data types from XSD. | ||||||
4.15 Patch | transform6265 | - | Latest | Fixed an issue with the XML Parser wherein XML validation was failing if the XSD contained | ||||||
4.15 | snapsmrc500 | - | Stable | Added a new property, Binary header properties, to the Document to binary Snap that enables you to specify the properties to add to the binary document's header. | ||||||
4.14 Patch | transform6098 | - | Latest | Fixed an issue wherein the XML Parser Snap was not maintaining the datatype mentioned in the XSD file. | ||||||
4.14 Patch | transform6080 | - | Latest | Fixed an issue with the Avro Formatter Snap wherein the Snap was failing for a complex JSON input. | ||||||
4.14 Patch | MULTIPLE5732 | - | Latest | Fixed an issue with S3 file reads getting aborted intermittently because of incomplete consumption of input stream. | ||||||
4.14 Patch | transform5684 | - | Latest | Fixed the JSON Parser Snap that causes the File Reader Snap to fail to read S3 file intermittently with an | ||||||
4.14 | snapsmrc490 | - | Stable | Upgraded with the latest SnapLogic Platform release. | ||||||
4.13 Patch | transform5411 | - | Latest | Fixed an issue in the CSV Formatter Snap where the output showed extra values that were not provided in the input. | ||||||
4.13 | snapsmrc486 | - | Stable | Upgraded with the latest SnapLogic Platform release. | ||||||
4.12 Patch | transform5005 | - | Latest | Fixed an issue with the Excel Parser Snap that drops columns when the value is null at the end of the row. | ||||||
4.12 Patch | transform4913 | - | Latest | Fixed an issue in the Excel Formatter Snap, wherein opening an output stream prematurely causes the Box Write Snap to fail. Excel Formatter now awaits the first input document, before opening an output stream. | ||||||
4.12 Patch | transform4747 | - | Latest | Fixed an issue that caused the Join Snap to go out of memory. | ||||||
4.12 | snapsmrc480 | - | Stable |
| ||||||
4.11 Patch | transform4558 | - | Latest | Enforced UTF-8 character encoding for the Fixed Width Formatter Snap. | ||||||
4.11 Patch | transform4343 | - | Latest | Enhanced enum labels on the Binary to Document and the Document to Binary Snaps for the Encode or Decode property with DOCUMENT and NONE options. | ||||||
4.11 Patch | transform4361 | - | Latest | Fixed a sorting issue with the Join and Sort Snaps where the end of the file was not detected correctly. | ||||||
4.11 Patch | transform4281 | - | Latest | Added support on the Kryo serialization for UUID and other types to the Sort, Join and In-Memory Lookup Snaps. | ||||||
4.11 | snapsmrc465 | - | - |
| ||||||
4.10 Patch | transform4058 | - | - | Addressed an issue with the Excel Parser Snap that failed with out of memory when using large input Data (eg. 191 MB). | ||||||
4.10 Patch | transform3956 | - | - | Conditional Snap: fixed an issue with the "Null-safe access" Snap Setting not being respected for return values. | ||||||
4.10 | snapsmrc414 | - | - |
| ||||||
4.9.0 Patch | transform3343 | - | - | Join Snap - All input documents from all input views should be consumed before the end of Snap execution. | ||||||
4.9.0 Patch | transform3281 | - | - | Made all four output views in Diff snap as mandatory. | ||||||
4.9.0 Patch | transform3264 | - | - | Made all four output views in Diff snap as mandatory. | ||||||
4.9.0 Patch | transform3220 | - | - | CSV Parser Snap - A new Snap property Ignore empty data with true default is added | ||||||
4.9.0 Patch | transform3019 | - | - | Addressed an issue with the transform2989 build. | ||||||
4.9.0 Patch | transform2989 | - | - | Addressed an issue with Excel Parser not displaying the most recent cached value for vlookups containing missing external references. | ||||||
4.9.0 | - | - | Introduced Encrypt Field and Decrypt Field Snaps. | |||||||
4.8.0 Patch | transform2956 | - | - | [CSVParser] Fixed an issue where an empty Quote Character config field was defaulting to the unicode quote character U+0000 (null). This caused issues if the input CSV had U+0000 characters in it. | ||||||
4.8.0 Patch | transform2848 | - | - |
| ||||||
4.8.0 Patch | transform2768 | - | - | Addressed an issue with CSV Parser causing a spike in CPU usage. | ||||||
4.8.0 Patch | transform2736 | - | - | Addressed an issue with Excel Formatter dropping the first record when Ignore empty stream is selected. | ||||||
4.8.0 | - | - |
| |||||||
4.7.0 Patch | transform2549 | - | - | Addressed an issue with Excel Formatter altering decimal numbers to text. | ||||||
4.7.0 Patch | transform2344 | - | - | Resolved an issue with validation of pipelines taking more time than executing a pipeline when a large amount of data is used. | ||||||
4.7.0 Patch | transform2335 | - | - | Resolved an issue with XML Parser failing with error: 'Maximum attribute size (524288) exceeded'. | ||||||
4.7.0 Patch | transform2206 | - | - | Resolved an issue with JSON Generator failing with an "Invalid UTF-8 middle byte 0x70" error on Windows. | ||||||
4.7.0 | - | - |
| |||||||
4.6.0 Patch | transform2018 | Resolved an issue where Excel Parser did not reliably set header row when "contains headers" is checked | ||||||||
4.6.0 Patch | transform1905 | Resolved an issue in Sort Snap where buffer size should not be fixed for optimal performance | ||||||||
4.6.0 Patch | transform1901 |
| ||||||||
4.6.0 Patch | transform1871 | Resolved a performance issue in Excel Multi Sheet Formatter. | ||||||||
4.6.0 |
| |||||||||
4.5.1 |
| |||||||||
4.5.0 |
| |||||||||
4.4.1 |
| |||||||||
4.4 |
| |||||||||
4.3.2 |
| |||||||||
4.3.1 |
| |||||||||
4.3.0 |
| |||||||||
4.2.2 |
| |||||||||
August 7, 2015 (2015.25/4.2.1) |
| |||||||||
June 27, 2015 (2015.22) |
| |||||||||
June 6, 2015 (2015.20) |
| |||||||||
May 2, 2015 |
| |||||||||
March 2015 |
| |||||||||
January 2015 |
| |||||||||
December 20, 2014 |
| |||||||||
November 2014 | Aggregate now provides 2 new functions: concat and unique_concat | |||||||||
October 18, 2014 |
| |||||||||
Fall 2014 |
| |||||||||
August 2014 |
| |||||||||
July/Summer 2014 |
| |||||||||
June 30, 2014 |
| |||||||||
May 2014 |
| |||||||||
April 2014 |
| |||||||||
March 2014 |
| |||||||||
January 2014 |
| |||||||||
December 2013 |
| |||||||||
November 2013 |
| |||||||||
August 2013 |
| |||||||||
July 2013 | JSON Splitter: The JSON Splitter Snap splits a list of values into separate documents. | |||||||||
Initial release |
|
Have feedback? Email documentation@snaplogic.com | Ask a question in the SnapLogic Community
© 2017-2024 SnapLogic, Inc.