/
FAQs & Troubleshooting

FAQs & Troubleshooting

Frequently Asked Questions

Possible reasons:

  • The field does not exist in the Asset Object Type

  • The field name in the Mode configuration does not exactly match the Asset field name

  • The attribute type selected in the Mode (Text/Date) does not match the actual Asset field type

  • The attribute value is empty or missing

  • The Mode is not selected as active
    ✅ Fix:
    Verify the field exists, ensure exact name matching, correct type selection, and make sure the Mode is active.

⚠️ If a field with an unsupported type (for example: Number, Object, Status, User, etc.) is configured:

  • The scan will fail

  • An error message will be shown

  • The asset will not be updated

✅ Supported types:

  • Text → Updated with current user’s username

  • Date → Updated with current date

During a successful scan:

  • Text fields → Updated with the current logged-in user’s username

  • Date fields → Updated with the current system date

ℹ️ Manual values are not taken during scanning; values are auto-populated by the app.

An error may occur if:

  • Attribute name mismatch exists between Mode and Asset schema

  • Attribute type mismatch (e.g., Mode says Text, Asset field is Date)

  • Attribute value is empty

  • Unsupported field type is configured

  • No Mode is selected

✅ Fix:
Review the Mode configuration and correct the field name/type.

Yes ✅
You can add multiple attributes inside a single Mode.
All configured attributes in the active Mode will be updated in one scan.

Only one Mode can be active at a time.

This is by design to:

  • Avoid conflicting updates

  • Ensure predictable field updates

✅ Select the correct Mode using the blue checkmark before scanning.

Yes ✅

You can:

  • Edit Mode name (inline edit)

  • Add / edit / delete attributes

  • Delete entire Mode

Changes take effect immediately for the next scan.

Possible reasons:

  • No scans have been performed after refresh.

  • Scan History toggle is turned OFF

✅ Enable the Scan History toggle to view previous scans.

  • Browser camera permission not granted

  • Camera already in use by another application

  • Unsupported browser

✅ Fix:

  • Allow camera access in browser settings

  • Close other apps using the camera

  • Use a supported modern browser (Chrome, Edge)

Yes ✅
Each scan:

  • Updates the configured fields again

  • Adds a new entry to Scan History

  1. Always double-check exact field names

  2. Ensure attribute types match

  3. Use only Text or Date fields

  4. Keep only the required Mode active

  5. Test with one attribute before adding multiple fields

Troubleshooting

Issue / Error

Resolution

Issue / Error

Resolution

Asset field is not updated after scanning

Create the field in the Asset Object Type before scanning

Asset field is not updated

Ensure the attribute name in Mode matches the Asset field name exactly (case-sensitive)

Error during scanning

Update the Mode attribute type to match the actual Asset field type

Scan fails with error

Use only Text or Date field types,Ensure the attribute has a default value and is not empty

Fields not updated during scan

Select the correct Mode using the blue checkmark before scanning

Only some fields are updated

Review all attributes inside the Mode and correct name/type

Wrong value updated

Text → updates username, Date → updates current date

Scan history not visible

Perform a scan and enable the Scan History toggle

Camera not opening

Allow camera access in browser settings

Camera not working

Close other applications using the camera

Camera not supported

Use a modern browser like Chrome or Edge

Scan updates wrong Mode

Activate the intended Mode before scanning

Multiple Modes causing confusion

Only one Mode can be active at a time (by design)