ContributionsMost RecentMost LikesSolutionsRe: Dynamic DB Account Use Cases Thanks, that’s a good suggestion, will pass it along to the docs team. Shayne Re: Parquet without Hadooplex Realize this is an old thread, but just wanted to update. In our release last month (Summer), this functionality was added. https://doc.snaplogic.com/wiki/spaces/SD/pages/1438227/Parquet+Writer Shayne Re: Dynamic DB Account Use Cases For a dynamic account, you can use pipeline parameters (though not fields in the document). When you create a dynamic account (take from MySQL): You can toggle those fields with = into expressions and insert the name of the _pipelineParam that you want the field to be filled from. Is that what you were looking for? Thanks, Shayne Re: REST SNAP - Pass data as the Input Which REST Snap? I just tested them all, and for me they all by default have an open input view. If that isn’t occurring, please let us know. In the interim, if you open the Snap dialog box and click Views, you can add an input view if it isn’t there: Shayne Re: Passing parameters/session variables between nested pipelines/snaps If you have sample pipelines, seeing those would be helpful, if possible. While the exact answer is going to depend on application, I’d generally say to use documents if you are going to be using Pipeline Execute (https://doc.snaplogic.com/wiki/display/SD/Pipeline+Execute), since with reuse turned on (e.g., you spin up the child pipeline once, instead of spinning it up and tearing it down per document) the pipeline parameters can only be set once. You should be able to access pipeline parameters in the Mapper by using an underscore instead of a dollarsign - i.e. $foo if it’s a variable, _foo if it’s a parameter. If you need the parameters returned, you can add a Mapper at the end, check “Pass Through”, and then add in the parameters you want to return using this syntax. Is that along the lines of what you’re looking for? Shayne Re: Citizen Integrator Solution? Thanks for the suggestion and use cases. We’ll discuss it internally with the UX team. It’s very helpful to have a concrete use case for these discussions, so thanks for including the additional details. Shayne Re: Citizen Integrator Solution? Thanks for the feedback. Am I correct that this doesn’t change the current permissions model / inheritance, it just moves the Snaplexes into their own (linked back to projects) UI area? Thanks, Shayne Re: Parquet without Hadooplex I am not aware of a method to do so at the moment; however, Parquet <-> S3 has been an increasingly requested feature recently and we are actively investigating implementation options, though we don’t have a timeline for release at the moment. Shayne Hodge Re: Citizen Integrator Solution? brettdorsey: Side note: Seems a bit strange that a SnapPlex, which is merely a run-time environemnt, is shared along with other pipelines and accounts rather than their own type of entity that can have access granted outside of the project structure. @tlui and I were talking about this the other day. We’re certainly open to suggestions to make the workflow more logical; FWIW, I’m with you on this one, but if we’re going to separate it out we want to make sure the redesign is actually a better user experience, so feedback is very welcome. Shayne Re: "JSON Splitter" snap truncate data! Could you share the pipeline or some screenshots of it? It is possible that the JSON Splitter has less output than input - see the first example in the docs, http://doc.snaplogic.com/com-snaplogic-snaps-transform-jsonsplitter_1 , but I’d like to investigate further. Thanks, Shayne