Szymon
New Contributor II
Joined 5 years ago
User Profile
User Widgets
Contributions
Re: Binary output - error pipeline - custom http codes
Thank you again. I have tried this approach last week without success. Both binary and document view using the maping table - see initial post. In the meantime on monday we had system upgrade. Anyways, it does work, the document output view like I have designed it in the first place, and what you have confirmed. So thank you again, your response triggered us to try it out again. kind regards.1.2KViews0likes0CommentsRe: Binary output - error pipeline - custom http codes
Thank you, I am sorry, I was not making it 2000% clear, so updated the initial post for that. ad 1. Now, the error, that I get is referring to the error pipline, that is used in ultra. So, is it not possible to use binary output view in the error pipeline? ad2. The goal is not to output custom http codes from the ultra pipeline itself, BUT from the error pipeline. When in error pipeline I do - as you suggest - convert document to binary using $status and $content, the error mentioned occurs, as soon as engine initializes the ultra pipeline.3.6KViews0likes3CommentsBinary output - error pipeline - custom http codes
There is a requirement for the following: Error pipeline for an ultra pipeline which responses with custom HTTP code, e.g. 500. Why: …The third party API caller shall receive a proper HTTP code, not only HTTP 200 with error message. …Or when the pipeline goes into an error it will receive 504 gateway timeout, just because, on standard snaplogic i unable to catch the errors. So: …I have implemented the ultra pipeline(A) and implemented error pipeline(B). …In the ultra(A) i have configured the error pipeline(B), so all the snaps use that error pipeline. …In the error pipeline(B), depending on the error, i have implemented custom error codes using Mapper Snap (Document → Binary), see pic below. BUT, when I save the pipeline(A) and the engine tries to initialize the ultra pipeline, i get the message from the engine: Error pipeline does not meet the requirements Reason: An unlinked output must be available when an error pipeline is used with an Ultra pipeline Resolution: Please redesign the error pipeline to have a single unlinked document output view is it not possible to have a binary output in ultra error pipeline(B)? YES or NO what is the alternative to output custom error codes from error pipeline(B), so the calling party sees, not HTTP 200, but HTTP 500? I DO NOT WANT to use Error View at the particular snaps in Ultra pipeline(A)! Any ideas?Solved5.2KViews0likes6CommentsRe: [solved] Add decimal zeros to integer for double
Arrgh! Indeed, Bojan, you are right. I always forget, that one should not relay on just a half-reliable platform. Also, if runtime presents the result same as validation. Terribly sorry for that. I suppose, it comes from the habit of using other mature integration tools. I promise to remember that in the future. I must admit, it presents a certain kind of a thrill “Oh goodie! which feature is reliable in this release, my-oh-my!” - very exciting. Thank you and kind regards. Output: [{"amount":1000.00}] Updated pipeline attached. toDouble_2022_01_12.slp (8.6 KB)3.8KViews0likes0CommentsRe: [solved] Add decimal zeros to integer for double
Puh! Apologies, that I have not described everything I had tried before posting. Among others, I had tried parseFloat as well. I wonder if you have tried it yourself, jolly good. Pipeline is attached parseFloat($amount.toFixed(2)) will remove the decimal ‘.00’, so this brings nothing. As a result you would get: 1000 → “1000.00” → 1000 Again I need to add decimals to 1000 to get 1000.00, NOT to “1000.00” { "amount" : 1000.00 } anyone? thank you. toDouble_2022_01_12.slp (5.9 KB)3.8KViews0likes1CommentRe: Migration Patterns
Ahh! Now I see. Apoligies for not reading correctly. Clever naming, really, that try to cover missing functionalities, well done! I am not sure if snaplogic is aware of it, but since 1970’s, there was some progress in IT. Requirements, like migrating/deploying/etc. single objects/assets/etc.(and not whole projects with all the assets) from one stage to another (e.g. dev → uat, uat → prod, etc.) are already standard in integration platforms nowadays. But I recon snaplogic is first at stage of copying objects only in within one stage. AND it requires custom development, really advanced! So, this seems to confirm it as a bug, that even though file writer says “overwritten”, file is not being written, therefore it is not there. { “filename”: “sldb:///myotherorg/myspace/myproject/file.name”, “result”: “overwritten” } No furhter questions. kind regards!1.4KViews0likes1CommentRe: Migration Patterns
Migrate Files definitely does not work. I am not sure if this is another BUG, but the File Writer result says “overwritten”, no error whatsoever. I am tired of creating tickets 🤢 Everything you touch on snaplogic seems to be buggy 😭 { “filename”: “sldb:///myotherorg/myspace/myproject/file.name”, “result”: “overwritten” }1.4KViews0likes3CommentsRe: Does the CSV formatter snap aggregate the input documents
Hi @walkerline117 To me, this snap behaves strange, especially as you see its very different than any other formatter snap of files related snap. Yeah, SL is not the sharpest tool in the shed. So CSV formatter collects all input documents to one. JSON formatter has the option, not to do it. So why CSV formatter does not, I wonder 😉 Either way, to anyone, who struggles with this ’ great feature’. Maybe mapping to binary directly would be a solution for you. See screenshots below. Of course, you need to format your content first to particular format. Well, I do not lose hope, that we get SL v1.0 before I’m retired. cheers! Document->Binary make sure you map to $content:2.2KViews0likes0Comments