You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Column headings currently displayed in SCWB v3 are mostly similar to the corresponding field names from the input JSON file where the string style name from the JSON file is usually translated to separate words - e.g. JSON name "license__key" is displayed as "License Key".
The primary exception to this pattern is for the Conclusions fields which do not exist in the Scan file.
Change Request
For simplicity and clarity we should revert the column names in SCWB to match the field names from the JSON Scan file.
For the Conclusions fields we may want to keep the existing column names to distinguish them from the Scan data.
The text was updated successfully, but these errors were encountered:
Background
The Column headings currently displayed in SCWB v3 are mostly similar to the corresponding field names from the input JSON file where the string style name from the JSON file is usually translated to separate words - e.g. JSON name "license__key" is displayed as "License Key".
The primary exception to this pattern is for the Conclusions fields which do not exist in the Scan file.
Change Request
For simplicity and clarity we should revert the column names in SCWB to match the field names from the JSON Scan file.
For the Conclusions fields we may want to keep the existing column names to distinguish them from the Scan data.
The text was updated successfully, but these errors were encountered: