ContributionsMost RecentMost LikesSolutionsCustomize the Response - HTML We have a task url that is triggered from an application we use. The application has an embedded web browser which also shows the response back from our pipeline. This is how the user knows if the task was successfully run or not (I’ve uploaded an image of the browser after the task is completed). I would like to customize/configure this resulting response back to the user so that it looks nicer. Does anyone know where/how to have it return something nicer looking (without having to point to a separate web server URL)? Route User to Webpage We’re attempting to create a pipeline that can be triggered from our web page when a user clicks on a hyperlink. We’ve created the pipeline so that it performs some operations (no problems with that so far). But when the pipeline finishes running, it should take the user to another web page. This part, we cannot figure out. So if I wanted to send a user to amazon.com, how would I get my pipeline to do that? Thanks in advance, Mike Kramer Consolidating Multiple Table Rows to Single Row I don’t know why I’m having such trouble with this task but I can’t seem to do this. I’m using a REST Get against our CRM system to extract the phone numbers related to a contact ID. Since there are four distinct types of phone numbers that can exist per contact, I end up with four rows per contact ID. In reality, I’d like one row for the contact but with one column for each phone type. Anyone know how to do this? Help is always appreciated. (see image for my starting point). Thanks. Mike Combining REST Get Queries into Single Snap I have a two part question. I have to perform 3 queries to extract information from an application. I can put all 3 queries in the same REST Get snap. First question is…is this better or worse than using 3 separate REST Get snaps? Second question depends on answer to first question. If using a single REST Get snap is fine/recommended, the result is 3 tables. One field in each is the same between them. How would I merge these together to make one nice data stream? For example, if I have organization id shared between the three tables, how do create one table where these are joined together? If using a single REST Get is not recommended, I’m assuming that using 3 REST Gets and a join would be the proper approach to getting the result I’m looking for…is that correct? Thanks in advance. Mike Re: Groundplex - REST Post Fails On one of my pipelines, I just see that it “failed to process HTTP response” but this pipeline used to execute in the past. Something changed that now prevents me from executing this pipeline. Another pipeline I’m testing says: “failed to execute HTTP request”. There is another error further down that says: “java.net.UnknownHostException: 3dmodels.mysite.com: unknown error”…this could be an issue of whitelisting IP addresses because the server I’m trying to connect/post to is on AWS. I’ve seen/read the IP addresses for SnapLogic’s cloudplex nodes can be whitelisted on AWS servers. But I’m not sure how I would find the IP address for the groundplex nodes and white list those. (Although, I’m not sure this is the issue). Groundplex - REST Post Fails We’re new to SnapLogic. We created a slick pipeline several weeks ago. That pipeline had a final REST Post that created an incident in a cloud-based ticketing system that we use. Now I’m finding that none of my REST Posts in any of my pipelines work. The only thing I can think of that changed is that we’re now using a GroundPlex instead of a CloudPlex. Could that be the cause of my issues? Anyone else seen this before? Thanks in advance, Mike Re: Search a DB based on input / Merging Results Never mind. I found the mistake. You actually have to put %20 in the URI to fill any spaces. Once I did that, it worked. I think I’m all set now. Thanks for the help. Re: Search a DB based on input / Merging Results Hi TK, Thanks for the tip. This made me look deeper into the REST API of the system I’m trying connect. There is a query option and I have the syntax working in Postman but when I copy and paste the syntax into a REST GET, it errors and says it’s a bad URI. Any advice on why a query like this would error? It’s clearly something syntactically wrong but I’m not sure what it is: “https://.com/services/rest/connect/v1.3/queryResults/?query=select * from contacts” Failure: The provided URI is invalid: https://.com/services/rest/connect/v1.3/queryResults/?query=select * from contacts, Reason: The provided URI is invalid: https://airborn--tst1.custhelp.com/services/rest/connect/v1.3/queryResults/?query=select * from contacts, Resolution: Please verify the provided URI and parameters are syntactically correct Re: Search a DB based on input / Merging Results So it seems to me that I need to use Routers and Joins to aggregate all of the mapped fields together from multiple REST Gets. Is this correct? Search a DB based on input / Merging Results Hi All, I’m a newbie so bear with me. I’m working on a pipeline that connects to a CRM system. This CRM system tracks everything by the customer’s contact ID number. However, our web site uses a customer’s email address for all processing. I’m trying to find a way to take an email address input and find the corresponding customer’s contact ID number. Does anyone out there have any tips on how to do this? This is the path I’m currently taking but it seems very laborious: I use a REST GET to get all contacts. This only gets me high level attribute fields (with one being contact ID). I use another REST GET to get the full details of each contact. This gets me a link to find the email addresses but not the actual email addresses. I use another REST GET to get all of the email addresses of all of the contacts. This gets me email addresses but errors when a contact doesn’t have an email address (not sure how to skip those null values). I’m also not sure how to merge all of these attribute values back together into a complete list of results. (ie. I have no idea how to match the email addresses of the last REST GET with the full details found in the previous REST GET. Any ideas?