Download ALP that generates reports in CSV

(Nick Papadatos) #1

Reading through the forum I cam across this:

Which helped me create a Design with the following:

 <MySource_PRINT id_name="__global__" var="content_type" content_type="text/csv" />
 <MySource_AREA id_name="page_body" design_area="body" />
 <MySource_PRINT id_name="__global__" var="content_attachment" extension="csv" />

All good but when you’re returning data that has commas then it breaks. I then I had to use keyword modifiers to remove/replace all commas.

Is this the only way?

eg, %question_answer_123456_q1^replace:,: %

Is it worth placing double-quotes where you know there’s going to have commas?
like so …,"%question_answer_123456_q1%"


(David Schoen) #2

I think so.

I’d just double quote everything and escape the double quotes:


(Nick Papadatos) #3

Thought as much David, thanks.

I also noticed that when I used a condition %begin_asset_created_readabledate^gt_date:01 Jun 2018% it leaves empty rows where 2017 data was.

eg, Say I have 20 rows of 2017 data above and 20 rows of 2018 data below the 20 rows above are empty before I get 2018.

Is there a way around that?

Thanks in advance

(Bart Banda) #4

Easiest way might be to use a search page instead and limit the search results on a date range? So that those assets don’t even show up?

Check out the Restrict Results Date Range section on the Search Fields screen of a Search Page asset.

(Nick Papadatos) #5

Thanks Bart I’ll give it a go

(James Azurin) #6

Yes, double-quotes before and after as field delimiters. Should be good; Good luck