{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/984c8d042f7548aea59e1a14c30e9c41\" frameborder=\"0\" width=\"1662\" height=\"1246\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1246,"width":1662,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1246,"thumbnail_width":1662,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/984c8d042f7548aea59e1a14c30e9c41-d205c05624683c8e.gif","duration":96.207,"title":"Filtering Template Content During Full Sync","description":"This Loom explains how the author handled a template migration during a full sync when distinguishing null values from absent values was not possible. They first query concept node schemas without template content, then filter afterward by retrieving the full template content and matching it against a list of localities with missing templates to build the final filtered nodes. They compare existing data cases showing null, missing, and text values to confirm the behavior. After reloading Obsidian and selecting again, the absent values get filled using the same template, though it is not presented as a strict reset."}