ContributionsMost RecentMost LikesSolutionsMongoDB Unique Query Is there any support for MongoDB distinct queries in SnapLogic? I’m trying to execute a query like this: db.Reason.distinct(“Values.Reason”) The Find snap seems to only accept JSON formatted expressions, but wasn’t sure if there’s another way to accomplish this that I am missing. Re: Empty CSV File With Header Row I have a lot of stuff going on downstream to also add a single column “end of file” footer row, which was also a real pain in the butt. Re: Empty CSV File With Header Row Mine looks a bit different. I left outer join my input stream with my static header row and evaluate for the presence of data in my router. Then I either remove the unnecessary header data element or map the header row data to the variable name expected downstream for the data, and union back together. Re: Can't create a non-UTC Date object to call .getTime() on I’m running into this problem as well. I need to convert a value obtained from toLocaleDateTimeString() back to a SnapLogic date object in its current timezone, but there doesn’t seem to be any way to maintain or set the timezone when parsing back to a date object. It always reverts to UTC as the timezone, though with the “correct” time from the original timezone. This is really unfortunate. Does anyone know how to create a new date object (not derived from a datasource with a non-UTC timezone) that is not in UTC time? Re: Connecting to DocumentDB in AWS with shared .pem Were you able to get a connection to DocumentDB working? I seem to be running into this error: Query failed with error code 303 and error message ‘Field ‘noCursorTimeout’ is currently not supported’ on server… Seems that SnapLogic makes the connection with that setting and it’s not supported in DocumentDB. Re: SQL Server Account Checkout Timeout Bumping this. Surely someone from SnapLogic knows? SQL Server Account Checkout Timeout The documentation for the Checkout Timeout property of the SQL Server Account configuration mentions: “An exception will be thrown after the wait time has expired.” Does anyone know what exception will be thrown? Dealing with seemingly random “com.microsoft.sqlserver.jdbc.SQLServerException: Connection reset” exceptions, and wondering if we can narrow it down to an interaction with this configuration. Re: Mapping an Ultra Task to AWS API Gateway These are the rough steps we took. The Network Load Balancer needs set up as a private IP address target group, pointing to your SnapLogic server by IP address: Then you create a VPC Link in API Gateway, which is basically giving it a name and associating it to your NLB: Once your VPC Link is set up, your Integration Request will look something like this: Re: Mapping an Ultra Task to AWS API Gateway Yes, we did solve it. The problem was that API Gateway resides in the public VPC portion of our AWS account, but the SnapLogic call was happening over our private direct connect tunnel into our local environment. We were able to solve the problem by enabling the endpoints as VPC link resources, and setting up a network load balancer that points to the internal SnapLogic URL. Re: JSON Root value walkermic: { “PEXR2002”: { “IDOC”: { “@BEGIN”: “1”, “EDI_DC40”: { “@SEGMENT”: “1”, “TABNAM”: “EDI_DC40”, “MANDT”: “100”, “DOCNUM”: “0000000002472008”, “DOCREL”: “731”, “STATUS”: “30”, “DIRECT”: “1”, “OUTMOD”: “2”, “IDOCTYP”: “PEXR2002”, “MESTYP”: “PAYEXT”, “STDMES”: “PAYEXT”, “SNDPOR”: “SAPS41”, “SNDPRT”: “LS”, “SNDPRN”: “S41CLNT100”, “RCVPOR”: “SNAPLOGIC”, “RCVPRT”: “LS”, “RCVPRN”: “SNAPLOGIC”, “CREDAT”: “20181205”, “CRETIM”: “220141”, “SERIAL”: “20180917101221” }, “E1IDKU1”: { “@SEGMENT”: “1”, “BGMTYP”: “PEX”, “BGMNAME”: “EXTENDED PAYMENT ORDER”, “BGMREF”: “2000000796”, “BGMLEV”: “ORG”, “BGMACC”: “001” }, “E1EDK03”: [ { “@SEGMENT”: “1”, “IDDAT”: “011”, “DATUM”: “20180917”, “UZEIT”: “101221” }, { “@SEGMENT”: “1”, “IDDAT”: “028”, “DATUM”: “20180917” }, { “@SEGMENT”: “1”, “IDDAT”: “017”, “DATUM”: “20180918” } ], “E1EDK02”: { “@SEGMENT”: “1”, “QUALF”: “029”, “BELNR”: “2000000796” } If I’m reading this right, it sounds like the name of your root element of your json document stream can change, but you always want to grab the root element to be able to process later? If so, I think something like this could work?