Yes! It has cut down the time we spend on validation so much!
We haven’t tried this yet but going to test it out! But I was wondering if the ‘Template’ are what can be used as a new JO source or if once it’s used in JO it becomes a DD object which also means it shows up in all our reporting objects? I am still using queries in JO because I didn’t want that many DDs created.
I was wondering if the ‘Template’ are what can be used as a new JO source or if once it’s used in JO it becomes a DD object which also means it shows up in all our reporting objects? I am still using queries in JO because I didn’t want that many DDs created.
Curious whether it becomes a DD object as well -- I’m with @spencer_engel on loving the design templates, and while I’m not using dynamic JO extensively yet, I’m planning to use templates as the building blocks for our queries when I do.
Our programs typically use a standard source query, but a lot of our 1x programs have slight modifications (products used, communication type, region, industry, etc) -- and the fact that we can save a NEW query as a template from within a dynamic JO.
I have been using them for a year or more now, and I’m also very happy with those as they create the interoperability we need between Reports, Programs, Rules and such. They provide a good alley to experiment too OR fix things in a safe space (or rather, not a space ;)).
My regret is that an update to a design template (such as a filter, for example) can’t be pushed to outputs that leverage the template, and I’d wish for it to be possible. To this effect - feel free to upvote the below idea:
@dayn.johnson and @ckeyes_bmc A design template used in a query will not become an object in data management, as it doesn’t contain data. It’s just a skeleton. Queries don’t become objects either, just like rules don’t.
@alizee, I can’t like this enough!
Tagging @kstim in for vis, especially on your idea you shared here (Option to push DD Template...) -- upvoted and added some musings there.
I have been using them for a year or more now, and I’m also very happy with those as they create the interoperability we need between Reports, Programs, Rules and such. They provide a good alley to experiment too OR fix things in a safe space (or rather, not a space ;)).
My regret is that an update to a design template (such as a filter, for example) can’t be pushed to outputs that leverage the template, and I’d wish for it to be possible. To this effect - feel free to upvote the below idea:
@dayn.johnson and @ckeyes_bmc A design template used in a query will not become an object in data management, as it doesn’t contain data. It’s just a skeleton. Queries don’t become objects either, just like rules don’t.
