23 votesunder review · 7 comments · Windward Beta Program » Windward Version 13 · Flag idea as inappropriate… · Admin →
I apologize for late reply to your question. I didn't notice it earlier unfortunately. Thanks for asking.
Actually, I would not like to terminate a report generation if a value is outside the range. Excel allows to keep a value out of range in case the validation is set later. Only when a user updates the value of the cell it enforces to choose from the list.
Maybe this could be an option in tag settings - terminate or not - to offer a flexible solution.
I refer here to Data Validation feature of Excel available under Data ribbon tab.
Particularly I'd like to set up validation criteria using a List. Meaning, in a cell where the validation is applied I can enter only values from within a list. The list of allowed values comes from a specified cell range.
Unfortunately this settings done in a template Excel spreadsheet are lost during a document generation with AutoTag.
Yes, I'd like to see Data Validation propagated from a template to a generated document. We often use validation based on Lists. In my case it could just be a fixed cells range, nothing related to tags. Data Validation settings somehow get lost while a document is generated.
The Use Case is the following.
Assume I have a collection of data elements, for instance Employees data including name, job position etc.
I'd like to be able to populate an Excel spreadsheet with the content of the collection using forEach tag and name the cells using a specific pattern at the same time, so I can refer to these cells from within my Excel spreadsheet using a cell name instead of a classical reference i.e. A1.
It should be enough to enhance forEach tag settings by prefix/postfix strngs which would be added to an index of an element.
If I had three Names of Employees (three collection' elements) extracted by forEach tag then cells might be named upon one of patterns
1) EmployeeName1, EmployeeName2, EmployeeName3
2) 1EmployeeName, 2EmployeeName, 3EmployeeName
3) Employee1Name, Employee2Name, Employee3Name
I have tried to explain my needs also under the Support Request #23716.
Please let me know if more input regarding the Use Case is needed.
LukaszLukasz shared this idea ·