ContributionsMost RecentMost LikesSolutionsRe: Community Update December 2017 A Slack channel perhaps? Re: Integrating with REST APIs + OAuth when no native Snap is available Thanks @robin, the blog looks very detailed. Will step through and try one of my non-native services and see how simple it is vs having a prescribed/precanned “integrate SL with XXXX API” set of standard docs/instructions. Integrating with REST APIs + OAuth when no native Snap is available Hi, I’m looking into some API integrations with some services that are not supported by native snaps, but do offer a rich REST API and support OAuth. The wiki docs on the REST Snap have some details but its a quite daunting process to try and blindly hook up the OAuth2 steps and get the account working in a pipeline. Maybe I’m being lazy, but arent there any walkthrus or has someone done this before and willing to share how to set up integration with: Domo Microsoft Graph API (for Azure AD) Maybe even ElasticSearch Thanks, Mike Re: Hosting a SOAP Service with SnapLogic Thanks for this @ncrouch, I like the XLST suggestion too. I guess hosting a REST service is a similar approach just catering for the differences in the protocol/headers etc. Re: Is XML Parser _very_ strict? Spooky, that sample works for me too it is just a redacted/cut down representation of the larger original. Maybe there were some newlines or tabs that were purged via cut/paste… Cant see anything invalid in the original, that still shows the “mixed content is not supported” error… Had a closer look, in the original machine-generated xml the elements were indented with some kind of space characters and the parser failed. Changing these to tab characters and the parser worked fine… Just a bit confusing as the failing XML appears to be valid UTF-8 XML. Thanks anyway, Mike Is XML Parser _very_ strict? Hi folks, I was looking to expose a Task via URL trigger with a payload of an XML message, so i started mocking this up with a sample XML as a file in SLFS and a simple pipeline File Reader → XML Parser → do-stuff. I didnt specify the “Inbound schema” on the XML Parser for the incoming binary XML, and even on a very simplified XML structure I’m getting: Failure: Failed to convert xml to json, Reason: Mixed content is not supported: ’ ', Resolution: Please check if the xml data is well formed the XML is considered valid by other non-SL tools: <EnterpriseMessage xmlns="http://schemas.xxxx.com/enterprise/services/2014/05" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"> <EnterpriseHeader> <MessageId>1369611c-eb2b-41ca-9573-852125cb418e</MessageId> <ThreadId>774c8fe4-145d-40c0-bfea-442bb29aa85c</ThreadId> <CreatedUtc>2016-01-12T14:13:32.654Z</CreatedUtc> </EnterpriseHeader> <MessageBody> <BusinessData xmlns=""> <Label> <OBJ_VER>0</OBJ_VER> <xxxx_COMPANY>10448</xxxx_COMPANY> </Label> <Company> <xxxx_COMPANY_ID>10448</xxxx_COMPANY_ID> <xxxx_COUNTRY_ID>320</xxxx_COUNTRY_ID> </Company> </BusinessData> </MessageBody> </EnterpriseMessage> Is it essential to set the schema to assist the parser? Sometimes the namespaces will vary or the schema be dynamic… Re: Using Github as a code repository for SnapLogic artifacts Many thanks for such a lot of detail and depth @Bhavin ! I will pass this onto our project team, a bit too intricate for me :). Are there any plans to add native support for github/tfs into the product in the future? And integrations with TeamCity/Jenkins/etc? Re: Using Github as a code repository for SnapLogic artifacts I think @Bhavin may have some advice here as his LinkedIn says: Prototyped integrating SnapLogic pipelines with CI/CD tool chain (ex: Jenkins/TeamCity) (sorry, I like a google search ;)) Am also interested in this as we spend a lot of time and expertise designing and testing pipelines (as well as ad-hoc workflows) and to rely on manual export with no change history/backup/CI is not ideal. We’re using both TeamCity and Jenkins (for CI and CD) on various other platforms with github as our source code repo. Any integration/scripts/plugins/webhooks for SL snaplexes would be great. (@nganapathiraju I see you posted on the TFS thread that customers are integrating with github - searching “github” in the documentation area has 0 matches, are there some whitepapers/guidance on how to integrate SL with github?) Re: Passing parameters/session variables between nested pipelines/snaps @Bhavin thanks again, I didnt toggle the “=” - $variable now works a treat in File Reader 🙂 Re: Passing parameters/session variables between nested pipelines/snaps Sorry my point was that File Reader doesn’t accept a $variable parameter, so I am at a dead end as I can’t write a value to the pipeline _parameter either which it does accept.