Bulk renaming of APs through Postman Runner fails

The_Roo
Getting noticed

Bulk renaming of APs through Postman Runner fails

I’m trying to do a bulk rename of APs in Postman. I have Postman set up with the following variables

The_Roo_0-1734434500083.png

 

And they work, so if I do any of the following, I get the expected output

GET {{baseUrl}}/organizations

GET {{baseUrl}}/organizations/:organizationId/networks

GET {{baseUrl}}/organizations/:organizationId/devices

GET {{baseUrl}}/networks/:networkId/devices

GET {{baseUrl}}/networks/:networkId/wireless/ssids/

So now I want to use runner, so I created a CSV file called “name-change-data” with a header line and a single line relating to a single AP I want to test on

The_Roo_1-1734434500083.png

 

The serial number is the number seen in the Meraki Dashboard, so I know that is right, and the name is just a different string to what is there at the moment.

I then create a collection called “Bulk Rename APs” that looks like this:

 

{{baseUrl}}/networks/{{networkId}}/devices/{{serial}}

 

the format of which was as specified in https://community.meraki.com/t5/Wireless/Rename-AP-with-postman-runner/m-p/21137#M3507

Next, I set up the body section as follows:

 

{

"name": "{{name}}",

"serial": "{{serial}}"

}

 

I then go to file>New Runner Tab, and get a window that asks me to “Drag a collection from the sidebar to run”, so I drag “Bulk Rename APs” in. It goes in with a lot of others, so I deselect all of them and reselect “Bulk Rename APs”

The_Roo_2-1734434500086.png

 

On the right of the page, I click “Select File” and select “name-change-data.csv” and then click the “run” button. I get the following result:

 

The_Roo_3-1734434500088.png

 

And the console shows

The_Roo_4-1734434500089.png

 

What am I doing wrong, and why is github flagged?

GET https://raw.githubusercontent.com/dexterlabora/json-magic/master/postman/postman-viz-jsonmagic-templ...

 

 

All advice gratefully recieved!

 

Thanks

Roo

 

5 Replies 5
alemabrahao
Kind of a big deal
Kind of a big deal

Your CSV format appears to be incorrect, please try the following.

serial,name
ABC123456789,New AP Name
I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
The_Roo
Getting noticed

Hi,

I tried changing the CSV format, and this time read it in notepad to be sure I wasn't missing something. It now looks like this (X's to replace real data):

 

serial,name
Q5AXXXXXXUE,HQ-PMDF-AP999

 

so as you can see, the format now matches your example. I tried again to change the  AP name and got the following:

The_Roo_2-1734529540153.png

and the consoles said this:

The_Roo_1-1734529457048.png

so I'm still doing something wrong..

 

Thanks

Roo

alemabrahao
Kind of a big deal
Kind of a big deal

It's not exactly the same error, but maybe it will help you.

 

https://medium.com/@odidaodida/how-to-fix-postman-typeerror-cannot-read-properties-of-undefined-read...

 

https://community.postman.com/t/old-request-updated-typeerror-cannot-read-properties-of-undefined-re...

 

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
alemabrahao
Kind of a big deal
Kind of a big deal

It might be interesting to open a discussion in the Postman community.

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
alemabrahao
Kind of a big deal
Kind of a big deal

Take a look at this:  https://learning.postman.com/docs/collections/running-collections/working-with-data-files/

I am not a Cisco Meraki employee. My suggestions are based on documentation of Meraki best practices and day-to-day experience.

Please, if this post was useful, leave your kudos and mark it as solved.
Get notified when there are additional replies to this discussion.