The following is a list of known issues and limitations that will be addressed in forthcoming updates.
Issues
| 1. Nested collections can’t be selected in the UI | |
| Description | The collection picker only surfaces top‑level collections. |
| Example | orders[] is selectable, but orders[].lines[] is not. |
| 2. GroupBy isn’t generated by the UI | |
| Description | There’s no UI control to build GroupBy syntax. |
| Example | <<foreach [g in items.GroupBy(i => i.Type)]>> must be typed manually. |
| 3. Manual tab can’t create collection/foreach tags | |
| Description | Manual tag creation supports fields but not collection iterators. |
| Example | You can create <<[customerName]>> but not <<foreach [c in customers]>>. |
| 4. Only the first extension method is applied in table generation | |
| Description | UI allows multiple extension method rows, but only the first is used. |
| Example | If you add Where and Take, only Where is applied. |
| 5. Nested collections are omitted from table previews | |
| Description | Table preview generation filters out nested foreach blocks. |
| Example | A nested lines loop inside an orders table won’t appear in preview. |
| 6. Bookmark display text is not auto‑wrapped as a field | |
| Description | Bookmark display text is inserted as literal text even when it’s a property. |
| Example | Display text customerName becomes customerName instead of <<[customerName]>>. |
| 7. Property correlation may be inconsistent across collection items | |
| Description | The UI derives a union of keys across items; when items differ, alignment can be inconsistent. |
| Example | items[0] = {name, cost} and items[1] = {name, sku} may lead to mixed/blank columns. |
| 8. Single Row table mode requires Single Column | |
| Description | “Single Row” is disabled unless “Single Column” is enabled. |
| Example | You can’t make a multicolumn table render as a single row. |
Limitations
| 1. Token names must start with a letter | |
| Description | Property names cannot begin with a number. |
| Example | <<[1stName]>> is invalid; use <<[firstName]>>. |
| Reference | https://support.encodian.com/hc/en-gb/articles/360020230377-Template-Syntax-Overview |
| 2. Conditionals have C# expression constraints | |
| Description | No multi‑dimensional array indexing; collection initializer syntax not supported; implicit user‑defined conversions must be explicit. |
| Example | <<if [matrix[0,1] == 1]>> is not supported. |
| Reference | https://support.encodian.com/hc/en-gb/articles/360020512538-Conditional-Expressions |
| 3. Conditionals inside foreach can’t reference external values | |
| Description | Loop conditions can’t call values outside the loop; use a pre‑set variable. |
| Example | <<var [LastItem = items.Last()]>> then <<if [item != LastItem]>>. |
| Reference | https://support.encodian.com/hc/en-gb/articles/360020512538-Conditional-Expressions |
| 4. Bookmarks/links must be on one line (or soft line breaks only) | |
| Description | Paragraph breaks inside bookmark/link blocks prevent creation. |
| Example | <<bookmark[...]>> + Enter + text + <</bookmark>> fails. |
| Reference | https://support.encodian.com/hc/en-gb/articles/360020347277-Hyperlinks-and-Bookmarks |
| 5. Primitive arrays require the _Text convention | |
| Description | Arrays of strings must be referenced using {Collection}_Text. |
| Example | <<foreach [in People]>> <<[People_Text]>> <</foreach>> |
| Reference | https://support.encodian.com/hc/en-gb/articles/360020415778-Repeating-Content |
| 6. Inserted documents are not populated unless -build is used | |
| Description | <<doc [document]>> inserts the file as‑is unless -build is specified. |
| Example | Use <<doc [document] -build>> to populate tags inside the inserted file. |
| Reference | https://support.encodian.com/hc/en-gb/articles/360020944618-Inserting-Documents |
0 Comments