Data360 Analyze

Welcome to the Data360 Analyze community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Here are some useful links where you can find more information:

Product Announcements  Product Documentation  Ideas Portal

Discussions

Members

Resources

Events

 View Only
  • 1.  Reading from Mailchimp API

    Employee
    Posted 03-14-2018 06:42

    I am trying to read from the mailchimp API using the enclosed nodes. They will not run as I have excluded the security header but I wanted to show you the settings.

    On run, the HTTP works fine and I end up with 100 lines output on the JSON. The problem I have is that each line of output replicates all the input data from the HTTP node in the output field “response” (see below) and so the size is quite unmanageable(i.e. I get the entire data set replicated 100x):

    Ideally I would remove the column ‘response’ from the JSON output data but I can't work out the setting.

     

    Any help would be appreciated.

     

    Mark

     

    Attached files

    TEST - 12 Mar 2018.lna
    7G5oskYcdKQ11aYwYiylTidzg[1]
    iRPXLn7PctZmRsDCXJteomlwa[1]

     



  • 2.  RE: Reading from Mailchimp API

    Employee
    Posted 03-14-2018 10:06

    Hi Mark,

    have you tried setting the 'PassThroughFields' property to "None"?

     

    Alternatively, if there is still an issue could you use the Head node to get one record from the output of the HTTP node and pass that to us? You should be able to click in the top left cell to select the entire record in the Data Viewer and then use <right-click> -> <copy as Excel> to get the data which can be pasted into, say, Notepad. Any sensitive information can be modified as required as long as the structure remains intact.

    Regards,

    Adrian



  • 3.  RE: Reading from Mailchimp API

    Employee
    Posted 03-14-2018 14:17

    Hi Adrian

    If I set the “PassThroughFields” to none I get the enclosed error:



    Otherwise I enclose 1line of output from the HTTP node:

    {"campaigns":[{"id":"523414e8e3","send_time":"2018-03-09T10:00:00+00:00","recipients":{"list_id":"bcb0970c94","recipient_count":40236},"settings":{"subject_line":"Up to 40% off Tesco Wines - 1/3 off Classic Wines at Waitrose - 3 Free Bottles at Majestic Wine Concierge - Buy 2 save 25% at M&S","title":"WD - Newsletter 09032018"}}]}

     

    Attached files

    F15E8C2E-7CA2-4433-913B-2A6C88D0FD6E.png
    F15E8C2E-7CA2-4433-913B-2A6C88D0FD6E.png

     



  • 4.  RE: Reading from Mailchimp API

    Employee
    Posted 03-15-2018 02:48

    Hi Mark,


    Your JSON Data node has some additional outputs - 'rows' and 'columnHeaders' - are you using these outputs in subsequent nodes in the data flow? If not, the simplest solution is to remove them. This can be done as follows:

    - switch to the 'Define' tab in the JSON Data node's configuration panel

    - scroll down to the 'Outputs' section

    - click on the context menu for 'rows' output and select 'Delete, then repeat for the 'columnHeaders' output.

     

    Alternatively, you can fudge the matter by modifying the HTTP to output another field which can then have its metadata output to the 'rows' pin. This can be achieved as follows:


    For the HTTP node


    - Populate the 'StatusCodeOutputField' property with the name of the field to contain the status code data - e.g. "code". This causes the node to now output the HTTP status code (e.g. 200) in addition to the response data.


    For the JSON Data node


    - Set the 'PassTrhoughFields' property to 'Unused'. When the node is run, the 'rows' output will list the metadata for the unused column.

     

    See the attached .lna which shows the two options.

     

    Regards,


    Adrian

    Attached files

    TEST_AW - 15 Mar 2018.lna