There are some situations where you may find it useful to convert a subdocument into Base-64 or Hex in order to store it directly in your data source. While this is mostly for JSON and XML, it's possible for SQL as well (of course). You can use an Out Tag to 'import' the subdoc into your finished report.
You may find this useful if you have a complex HTML document that you want to import, but hit some limitations with what Windward supports.
Why use the Out Tag?
If the actual data is stored in your data source, use an Out Tag. The Import tag is used in other scenarios when the file actually lives in a browser or another location that is not your data source.
The documents and sample data sources already have an encoded version of a test document.
Click here to see what the test document should look like.
Make sure to connect your template to the data source provided. The Out Tags have already been set up and you should be able to output immediately.
- First, convert the document that you want to include in your final report. We used http://base64-encoding.online-domain-tools.com/.
- Copy the encoded text and paste that information into the node in your data source that you intend to use.
- Now in your template, connect to your data source and insert an Out Tag.
- Use the Data Tree or the Tag Editor to assign the correct node to your tag.
- Next set the Type to BASE64_TEMPLATE or HEX_TEMPLATE. You can do this in the AutoTag tab or in the Tag Editor (make sure to save your changes if you use the Tag Editor)
That's all there is to it! When you Output, your subdocument will appear with all the formatting as it was before you encoded it.
Be aware that you cannot use features such as applying Parent or Child styles (those are not options for the Out Tag). What you created before you encoded the document is what will appear in your final report.