When creating or updating a View definition, a few issues can arise.
This page covers the most common issues FinFam will catch and report, and how to fix them.
Uploading Duplicate Versions
If you try to upload a View with the same version number as an existing one, FinFam will reject the upload. You may see an error like:
Example error:
View source with root ID vbl_abc123 and version 0.1.3 already exists. Update the version field in the settings sheet and try again.
Always increment the version field in your View’s settings sheet before uploading a new version.
FinFam does not look at the filename for the version number, so you can rename the file to anything you want,
as long as the settings sheet is updated.
Broken References
If your View references a field name that doesn’t exist (for example, in a formula or default value), you’ll see an error about a broken reference. Double-check all field names for typos, and make sure every referenced field is defined in your calc sheet.
Example error:
1 validation error for SFormSpec Value error,
Failed to resolve the reference in sheet "calc" from field "annual_income_post_tax" to "D50" (formula: =builtins!D56 + D50)
In this case, the field annual_income_post_tax is trying to reference cell D50, which couldn’t be mapped to a field.
Another such error:
Expected all referenced fields to have a default value.
Equation for "annual_income_post_tax" references empty value cell for "second_home_intro".
Here the cell was resolved to a field, but the field had no default value, likely because it was a content field.
Duplicate Field Names
If two fields in your calc sheet have the same name, this will cause errors in formulas and user data. Make sure every field name is unique.
Example error:
Duplicate field name detected: 'loan_amount'
Invalid Field Names
Field names must be lowercase, alphanumeric, and use underscores only. Avoid spaces, dashes, or uppercase letters.
Example error:
Invalid field name: 'Loan Amount'. Field names must be lowercase, alphanumeric, and use underscores only.
Type Option Errors
Only use supported type options like output, hide, expert, and calculate. Typos or unsupported options will cause validation errors.
Example error:
unknown type opts: ['ouptut']
Default Value Type Mismatch
Default values must match the field’s type (e.g., numbers for amount, percent, etc.). Mismatched types will cause errors.
Example error:
failed to convert field default value ('abc') to python type for interest_rate (float): could not convert string to float: 'abc'
Output/Hidden Field Conflicts
A field cannot be both output and hide. Use only one of these options per field.
Example error:
output fields cannot be hidden
Parameter Map Issues
Parameters like min and max must be valid numbers. Invalid parameters will cause validation errors.
Example error:
failed to convert 'min' to float
Changing or Removing User-Visible Fields
Renaming, removing, or changing the type of user-visible fields can break upgrades for users who have saved their own values.
While not technically an error at upload time, it will break upgrades for users who have saved their own values.
Stick to adding new fields or updating labels/hints instead.
If a field simply must be removed, consider whether making a new View might be a better solution.
