Same thing—model your API call off the sample request in the API documentation. We use the ‘endpointUrl’ that we had constructed before, include our headersMap and our params variable (including all the required parameters and the data for the actual row we’re adding). By including an info statement for the actual update variable we can check and see if the update ran successfully or not.
Once you test that out, just refresh your Analytics table and verify that the note was added!
Of course, make sure that you have recently modified notes to draw from in the CRM. Your ‘notesResponse’ invokeurl will pull all notes modified in the time range you specify, whether they were added or edited. Your ‘exportDataResponse’ invokeurl will tell you whether a specific note was added or edited by identifying whether it was already in the Analytics Notes table. So, if you’re trying to test out the updateRow section of your code, make sure your note is already in the Analytics table, and if you are testing out the addRow API call, create a new note for testing.