<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Local JSON]]></title><description><![CDATA[Questions, answers, and discussions about using a local JSON object array as a Templater data source.]]></description><link>https://forums.dataclay.com/category/12</link><generator>RSS for Node</generator><lastBuildDate>Sun, 17 May 2026 17:53:44 GMT</lastBuildDate><atom:link href="https://forums.dataclay.com/category/12.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 09 Apr 2026 18:59:56 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Data Source size limit?]]></title><description><![CDATA[@ariestav @Jeff Thanks for the info.  sounds like we’d be better off just using Que?!
]]></description><link>https://forums.dataclay.com/topic/408/data-source-size-limit</link><guid isPermaLink="true">https://forums.dataclay.com/topic/408/data-source-size-limit</guid><dc:creator><![CDATA[pbretz]]></dc:creator><pubDate>Thu, 09 Apr 2026 18:59:56 GMT</pubDate></item><item><title><![CDATA[Quotation marks in text strings]]></title><description><![CDATA[@eric_dean
Great question! Escaping the quotation marks should be as easy as putting a backslash before the quotes in the text block of our JSON file. So, for example, if we wanted something like this:
Lorem ipsum "dolor" sit amet
we’d write it like this:
Lorem ipsum \"dolor\" sit amet
The backslashes should be read as an “escape” to keep the quotation marks in the text from interfering with the formatting of the JSON data file.
Hopefully, that should be all we need, but if you have any other questions, please feel free to reach out.
Thanks,
Jeff
]]></description><link>https://forums.dataclay.com/topic/374/quotation-marks-in-text-strings</link><guid isPermaLink="true">https://forums.dataclay.com/topic/374/quotation-marks-in-text-strings</guid><dc:creator><![CDATA[Jeff]]></dc:creator><pubDate>Tue, 01 Oct 2024 21:22:50 GMT</pubDate></item><item><title><![CDATA[Nested JSON??]]></title><description><![CDATA[@Neil-González
It’s definitely going to depend on how the data is collected and what you’re trying to achieve. You could certainly render each worksheet individually and then combine them into a final master project, but you could also merge all of the data into one large sheet to create a ‘flat’ JSON file. That may allow you to combine the scenes without having to render or replicate the project multiple times. Instead, you could theoretically create sub-comps and then use the Time Sculpting features of Templater to resize the individual sections as necessary.
After looking at the data in your JSON example, you might consider a setup where you create a series of blank videos or comps of variable durations and then load them with the ‘duration’ data point. You could then use Time Sculpting to trim the image and text to that blank placeholder’s duration as needed. Again, a lot of this will depend on your setup, so if you have any specific questions, please just let us know.
As for your question about what version you need, it sounds like your setup will be best served by either the Pro or Bot version of Templater. If your final goal is full automation, Bot will probably be the way to go, but if you’re mainly looking to replicate and iterate large numbers of videos, Pro should be fine.
]]></description><link>https://forums.dataclay.com/topic/128/nested-json</link><guid isPermaLink="true">https://forums.dataclay.com/topic/128/nested-json</guid><dc:creator><![CDATA[Jeff]]></dc:creator><pubDate>Thu, 01 Oct 2020 21:20:00 GMT</pubDate></item><item><title><![CDATA[essential graphics + templater data]]></title><description><![CDATA[@Tasnadi-Otto Does the attachment work in the expected behavior in your main composition?  Or, is the attachment broken when you use the Master Properties feature in AE?
Can you share the templater.log file with us?  Also, check this article out — it may offer some tips to help troubleshoot the issue.
Thanks,
Arie
]]></description><link>https://forums.dataclay.com/topic/120/essential-graphics-templater-data</link><guid isPermaLink="true">https://forums.dataclay.com/topic/120/essential-graphics-templater-data</guid><dc:creator><![CDATA[ariestav]]></dc:creator><pubDate>Fri, 07 Aug 2020 21:48:06 GMT</pubDate></item><item><title><![CDATA[{{off}} Flags preventing Bot exports]]></title><description><![CDATA[For anyone that’s viewing tis thread, the issue lay around toggling on and off pre-compped layers.
Using the “swapping” function gave me the results I was looking for. Thanks @ariestav for all the help.
Here’s a once of Ari’s videos that explains comp swapping.
https://www.youtube.com/watch?v=DEIg7mOR3iA
]]></description><link>https://forums.dataclay.com/topic/119/off-flags-preventing-bot-exports</link><guid isPermaLink="true">https://forums.dataclay.com/topic/119/off-flags-preventing-bot-exports</guid><dc:creator><![CDATA[RonanDL]]></dc:creator><pubDate>Mon, 27 Jul 2020 12:02:24 GMT</pubDate></item><item><title><![CDATA[Dynamic Color through json]]></title><description><![CDATA[@Jon Thanks that was very helpful. Appreciate!
]]></description><link>https://forums.dataclay.com/topic/66/dynamic-color-through-json</link><guid isPermaLink="true">https://forums.dataclay.com/topic/66/dynamic-color-through-json</guid><dc:creator><![CDATA[Ridvan]]></dc:creator><pubDate>Sun, 10 Feb 2019 13:03:11 GMT</pubDate></item></channel></rss>