mmussitsch
New Contributor II
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Finding alternative for Join/Union Snap?
Hi – I know this is an old post – but wanted to ask: Should JOIN “merge” “unsorted” behave similar to UNION? I found a recent issue where the output data from each is totally the same, but the JOIN caused 4000+ rows of data to hang and not return, but UNION resolved it in an instance. Just curious the difference with “merge” and why this may have happened. TIA - Melissa3.7KViews0likes1CommentRe: (Expression Library) Pull Account based on Parsed Path call
Thanks so much Viktor for the help. You’ve helped me simplify some things and build upon them. I now have a pretty comprehensive file. In addition to the other functions, I have new ones like getProjectSpace, getProject, findProject, findProjectSpace, findAreabyProject, findAreabyProjectSpace so that if an item doesn’t have a “Project” definition it will default to the Project Space definition. They all work together in one call pullObject(“Salesforce”). It’s working very well. One quick question, your code snippet, what editor/file format is that with all the colors. Sure is nicer to read than an unknown .expr file via Notepad++. Thanks! Melissa2.9KViews1like4CommentsRe: (Expression Library) Pull Account based on Parsed Path call
Hmm, no reply yet. If I’ve gone too complicated, perhaps I can ask a simpler question, given my Accounts definition above, is there a function call that can be written to check if a value exists? Basically, if the “project” section doesn’t exist, then I want to grab the account name from the “project space” section which will always be there. In my testing, I just keep getting errors or null values that I can’t seem to test for. I can do it via a Mapper, but that defeats the purpose of my expression library and being able to reference the Account Name directly in other snaps and not have to pass them around. Any advise is appreciated.2.9KViews0likes0Comments(Expression Library) Pull Account based on Parsed Path call
I’ve searched for examples but not having much luck. My data in the .expr file looks similar to this: Accounts: { projectspace: { ProjectName: { Salesforce { Dev: { account_name : “Salesforce CIDEV” }, } … I wrote a parsePath function call that would pull the project space and project. The function whereAmI uses getOrgName to determine the environment. Then ultimately, I’d like one call to get the Account based on the projectPath + type + env to get a single result. getOrgName: pipe.plexPath.split(‘/’)[1], parsePath: x => (x.split(“/”)[x.split(“/”).length-2].replaceAll(" “,”“) + “.” + x.split(”/“)[x.split(”/“).length-1].replaceAll(” “,”")), whereAmI: this.getOrgName.toLowerCase().contains(‘prod’) ? “Prod” : (this.getOrgName.toLowerCase().contains(‘test’) ? “Test” : “Dev”), getAccount: (path,type) => this.Accounts[this.parsePath(path)][type][this.whereAmI], parsePath returns “projectspace.ProjectName” and whereAmI returns “Dev”. I’d like to pass in type as “Salesforce”. I know getAccount isn’t right. I just wanted to represent what I’m trying to do. I’ve made many variations to it without luck. I basically want to call lib.expr_lib.getAccount(pipe.projectPath,“Salesforce”) and return the value “Salesforce CIDEV”. Appreciate any help! Thanks. Melissa4.6KViews0likes8CommentsCan we pass the "pipe" object as a parameter to a child pipeline?
I’m using this for an error handler. The executing pipeline hits an error that sends it to the error pipeline. The error pipeline writes the details to a db table or flatfile. I was hoping I wouldn’t have to send all the pipe details as parameters individually from all pipelines that use this and could reference just the object. I could see an option to write the details to a file that gets read in, but that also seems clunky. I apologize if this is basic and has been discussed but my search didn’t pull anything back. Melissa2.9KViews0likes2CommentsRe: Date formatting
Thanks for this suggestion. One thing I uncovered, and I can’t believe it wasn’t mentioned to me, but was on the Snowflake Select snap, the Handle Timestamp and Date Time Data option. I hadn’t seen that and when I selected the SnapLogic Date Time format in Regional Time Zone option, the $LAST_RUN_DATE field would come as a single field and not put the .Timestamp in a sub-object. Ugh. This was a painful lesson.1KViews0likes0CommentsRe: Date formatting
Well according to support, the snowflake Timestamp_NTZ is not compatible with snaplogic expression language. Only work around is to use a string field instead if possibe. If not in the database, then write it out to a file without manipulation and then read it in as a string in snaplogic. Not ideal, but I think candidate for snaplogic enhancement request. Thanks again for the help.2.2KViews0likes1Comment