Item-of-Type (IoT) Field Limitations in JCI Excel Functions & ReqIF Mapping

Kemi
Kemi
  • Updated

Published Date: June 2, 2025

Audience: Everyone

Products and Versions Covered: 

  • Cloud/CVC
  • Self-hosted, Replicated - KOTS
  • Jama Connect Interchange™ 

Summary

Item-of-Type (IoT) Field Limitations in JCI Excel Functions & ReqIF Mapping
Customers may want to read an Item-of-Type field from one item, write that value into another item, and preserve the IoT link (not just the text).

Resolution

In the current JCI architecture, Item-of-Type (IoT) fields are read-only. Excel Functions can display an IoT value, but they cannot write or update IoT links. ReqIF mappings likewise cannot create or edit IoT associations. Design workflows to reference IoT fields for look-ups only; move any required data via standard text, picklist, or relationship fields.

 

#

Action

Detail

1

Understand Current Behavior

  • JCI reads IoT values (e.g., “Subsystem Req → Hazard 123”).

  • JCI cannot write an IoT link back into Jama.

  • In ReqIF mapping UI, IoT fields do not appear in the drop-down.

2

Design Alternate Data Flow

  • If you must copy the reference, map the IoT display text to a Jama text field.

  • Preserve traceability by syncing the actual relationship, not the IoT attribute.

3

Communicate to Stakeholders

  • Explain that IoT is intended for lookup/reference only.

  • Recommend using a Relationship or Picklist when write-back is required.

4

Log Enhancement Requests

  • Capture use-cases where full IoT round-trip is critical.

  • File in Ideation portal → tag “ExcelFn IoT write-back.”

Additional Resources 

Feedback:
We welcome your input! Please sign in to leave any comments, suggestions, or improvement ideas below.

 

 

Related to

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.