Validation
Before Sheet Architect generates your export files, it scans your entire sheet for problems. Validation catches issues that would cause your sheet to malfunction on the target VTT or that indicate something you probably did not intend.
Validation results fall into two categories:
- Errors -- Problems that must be fixed before you can export. These would cause your sheet to break or behave incorrectly on Roll20.
- Warnings -- Issues that will not prevent export but that you should review. They often indicate things that could confuse players or cause subtle bugs.
Common Errors
Missing Attribute Name
An input component (text field, number input, checkbox, select, etc.) is not bound to an attribute. On Roll20, every input must have an attribute name so the value gets saved to the character. Without one, the input appears on the sheet but anything the player types into it disappears when the sheet is closed.
How to fix: Select the component in the Layout Editor, open the Property Inspector, and set its Attribute Name property.
Duplicate Attribute Names
Two or more components use the same attribute name in a way that conflicts. On Roll20, each attribute stores a single value. If two unrelated inputs share the same attribute name, they will overwrite each other.
How to fix: Rename one of the conflicting components so each has a unique attribute name.
Duplicate attribute names inside a repeating section are fine -- each row of a repeating section has its own attribute scope. The error only applies to duplicates at the same scope level.
Invalid Repeating Section Name
A repeating section's name does not follow Roll20's naming rules. Repeating section names must be lowercase and use only letters, numbers, and underscores. They cannot start with a number.
How to fix: Open the repeating section's properties and change the name to follow the allowed format. For example, spells_known or inventory are valid names. Spells Known or 3rd_level are not. SheetArchitect automatically normalizes names (lowercasing, replacing spaces with underscores, and stripping invalid characters), but it is good to name things correctly from the start.
Empty Layout
Your sheet has no components at all. Roll20 needs at least some HTML content to display.
How to fix: Add components to your layout in the Layout Editor.
Invalid Roll Formula
A roll button contains a formula that Roll20 cannot parse. This could be a syntax error in the dice notation, a missing closing bracket, or a reference to an attribute that does not exist.
How to fix: Open the roll button's properties and correct the formula. Refer to Roll20's dice reference for valid syntax.
Common Warnings
Unused Attributes
You have defined attributes that are not referenced by any component in your layout. These attributes will be created on Roll20 characters but players will have no way to see or edit them.
How to review: If the attribute is used only in logic graphs or roll formulas, you can safely ignore this warning. If it is genuinely unused, consider removing it to keep your sheet clean.
Missing Labels
Input components exist without associated labels. Labels are important for accessibility -- they tell screen readers what each input is for, and on Roll20 they also let players click the label text to focus the input.
How to fix: Add a label component near each input and set its For property to match the input's attribute name.
Large File Size
The exported files exceed recommended size limits. Very large sheets may load slowly on Roll20, especially for players with slower connections.
How to review: Check whether you have redundant components, very large CSS, or unused logic nodes that could be cleaned up. Prebuilt layouts sometimes include more structure than you need -- you can trim unused sections.
Unreachable Logic Nodes
Nodes in your logic graph are not connected to any output. They will be compiled into sheet worker code but will never execute.
How to fix: Either connect the nodes to the rest of your graph or delete them.
Working Through Validation Results
Fix all errors before exporting. Warnings will not prevent export, but addressing them will improve your sheet's quality and your players' experience.
Validation results are clickable -- selecting an error or warning takes you to the relevant component or section of the editor so you can fix the issue without hunting for it.
If you are unsure what a validation message means, hover over it for a longer description with specific guidance.