# Combine all source records as a file to export

**URL:** https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392
**Category:** Integrator.io
**Tags:** export
**Created:** [August 4, 2023, 3:21pm UTC](https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392 "2023-08-04T15:21:10Z")
**Posts on this page:** 10
**Page:** 1

<div class="post-metadata">

### Author: ![vreddhibhat](https://avatars.discourse-cdn.com/v4/letter/v/5daacb/32.png) [@vreddhibhat](https://connective.celigo.com/u/vreddhibhat)
#### Post date: [August 4, 2023, 3:21pm UTC](https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392/1 "2023-08-04T15:21:10Z")

</div>

Here is what I want to achieve, and the question is in point 3.

1. Export a set of records from a source (I am good here)
2. Process the record one by one and export it to some destination (I am good here too)
3. Combine all source records as content of a file and send it to some destination (This is what I am trying to figure out. How?)

---

<div class="post-metadata">

### Author: ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)
#### Post date: [August 4, 2023, 6:31pm UTC](https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392/2 "2023-08-04T18:31:55Z")

</div>

@vreddhibhat what is the destination? If the destination is a file provider like FTP, S3, Google Drive, etc then it will by default aggregate each unique source to a file. If the destination is not a file provider, then you can batch requests on a per page basis, but only file providers have the buffering ability.

---

<div class="post-metadata">

### Author: ![vreddhibhat](https://avatars.discourse-cdn.com/v4/letter/v/5daacb/32.png) [@vreddhibhat](https://connective.celigo.com/u/vreddhibhat)
#### Post date: [August 5, 2023, 5:05am UTC](https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392/3 "2023-08-05T05:05:34Z")

</div>

@tylerlamparter

The destination would be netsuite. And the source would be a generic HTTPS endpoint which accepts a POST request and responds with semicolon separated csv file content.

---

<div class="post-metadata">

### Author: ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)
#### Post date: [August 5, 2023, 11:28pm UTC](https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392/4 "2023-08-05T23:28:02Z")

</div>

So are you trying to group the records together that are coming from your initial POST call to your source so that only 1 record in NetSuite get created? Maybe you can elaborate some more.

---

<div class="post-metadata">

### Author: ![vreddhibhat](https://avatars.discourse-cdn.com/v4/letter/v/5daacb/32.png) [@vreddhibhat](https://connective.celigo.com/u/vreddhibhat)
#### Post date: [August 7, 2023, 3:38pm UTC](https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392/5 "2023-08-07T15:38:35Z")

</div>

Yes @tylerlamparter That is exactly my requirement.

---

<div class="post-metadata">

### Author: ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)
#### Post date: [August 7, 2023, 3:42pm UTC](https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392/6 "2023-08-07T15:42:03Z")

</div>

@vreddhibhat have you tried the group by functionality?

 ![5301043caa20740200000001-d4d4662666264b5aa58402fda5955437.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/1/149e48a7e7bf5dd66138b5fd7e5586f377cba12e.png)

---

<div class="post-metadata">

### Author: ![vreddhibhat](https://avatars.discourse-cdn.com/v4/letter/v/5daacb/32.png) [@vreddhibhat](https://connective.celigo.com/u/vreddhibhat)
#### Post date: [August 7, 2023, 3:45pm UTC](https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392/7 "2023-08-07T15:45:00Z")

</div>

Looks like either I am on a different version, or the REST type of export does not expose this group option!!

 ![5301043caa20740200000001-804cf6780b8745c4b6ecb732258f8feb.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/9/9ea28706063a613a2f4e66f90ff52676bce04b96.png)

---

<div class="post-metadata">

### Author: ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)
#### Post date: [August 7, 2023, 3:55pm UTC](https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392/8 "2023-08-07T15:55:09Z")

</div>

@vreddhibhat can you screenshot your flow? Are you using generic REST type? You should migrate to generic HTTP which has all the functionality of REST and more. REST has been deprecated to some extent so I'm wondering where/how you made this.

---

<div class="post-metadata">

### Author: ![vreddhibhat](https://avatars.discourse-cdn.com/v4/letter/v/5daacb/32.png) [@vreddhibhat](https://connective.celigo.com/u/vreddhibhat)
#### Post date: [August 7, 2023, 4:00pm UTC](https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392/9 "2023-08-07T16:00:37Z")

</div>

Its indeed the HTTP(S):

 ![5301043caa20740200000001-f849b7e730b24ab18cee5bdc998b79be.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/1/1cbf38a6ea88bf925cb86c09b1919fa519a4dae1.png)

---

<div class="post-metadata">

### Author: ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)
#### Post date: [August 7, 2023, 4:14pm UTC](https://connective.celigo.com/t/combine-all-source-records-as-a-file-to-export/392/10 "2023-08-07T16:14:49Z")

</div>

@vreddhibhat it looks like for CSV type responses, you need to specify the group within the parser rules here:

 ![5301043caa20740200000001-6e880416ab474e76a92a7fc398f6802b.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/8/8ae87769a23be9b50f0ba4690f5df3da05b7c81d.png)
