Field naming rules
Use stable and predictable Tag values for all content controls.
Recommended rules
- Use lowercase snake case:
client_name,invoice_date - Use meaningful names based on business data
- Keep names consistent across templates when fields represent the same concept
- Avoid spaces and special characters
Structure guidance
- Root text field:
client_name - Repeating section tag:
services_table - Child field inside repeating section:
unit_price
Avoid
- Empty tags
- Duplicate tags in unrelated fields where uniqueness is expected
- Random abbreviations that are hard to maintain