Data collection import still removes leading zeros sometimes

[JaredPage]

Bug Description
I am experiencing an error with the Data function in the Postman Runner. I have an MS Excel document which I export a CSV from. I then import this CSV into the Data field in the Runner for my collection. This seemed to be working fine initially until I noticed some oddities. I eventually discovered that leading zero's from the numbers in my CSV file were being stripped from the imported CSV. The CSV file has the leading zero's, but the import process doesn't recognize them.

My current work around is to use a random csv to json site to convert my CSV file to a JSON file (which then works perfectly).

I have submitted this here instead of the Newman one because I cannot actually reproduce this with Newman.

Steps to Reproduce

1. Open a text editor and save the following CSV data as test.csv

example,data,moredata
0795184662,0002332693,001234456

2. Open Postman
3. Open the Runner's panel by clicking 'Runner' up the top
4. For the Data section, click 'Select File'
5. Choose the test.csv you saved earlier in step 1.
6. Once returned to the Runner's panel, verify that the file has been loaded.
7. Click preview.
8. Notice that the leading zero's for the first two columns have been stripped, but the last column has not.

Expected behavior
I expect that the other columns would also be quoted and not lose their leading zero's, just like the last column.

Screenshots

App information:

• Native App
• Postman Version 6.2.5
• Windows 10 64-bit

Additional context
I found other bugs around (like this one and this one) that seem to indicate the problem was fixed in Newman v4.0.0. However, I am obviously still experiencing this bug.....potentially, is the latest version of postman not using this version of Newman ?

[sivcan]

Yeah, as you mentioned this issue is a duplicate of #2734

Follow #2734 for further updates on the issue.

We'll be updating the thread once we have an update for this.