video1.0<iframe src="https://www.loom.com/embed/bc8336651d7243f1b6f809ee6e886d9f" frameborder="0" width="1662" height="1246" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>12461662Loomhttps://www.loom.com12461662https://cdn.loom.com/sessions/thumbnails/bc8336651d7243f1b6f809ee6e886d9f-d044071ad5c410ee.gif198.784This Loom explains how importing a relation involving a new node type requires ensuring the format and store behavior match expectations. The author recreates a test relation instead of updating a previously imported one, notes that the test node and relation types appear only after reloading the plugin due to a caching issue, and discusses concerns about whether relation creation reflects in the new store, especially with reified relations enabled and the new store off. After adding a special-case code change, they ensure relations created this way have no triples by returning early when needed forStoreRelationEnabled. They then confirm that on the claim page, the isTestedBy relation is visible and the import works successfully.