Forum Discussion

MFzOS's avatar
MFzOS
Occasional Contributor
3 years ago

Using Property Transfer in Ready API, How Can I Transfer a Numeric Value into JSON object?

Hi, When fetching data source from EXCEL file, I need to transfer some of the values to JSON objects. All values are being parsed in as string format. How can I parse in values as integer instead wh...
Data-Driven Testing
Function Tests
REST
Test Setup
  • richie's avatar
    richie
    3 years ago

    Hey MFzOS 

     

    Ok - so I've set it up and it runs fine - when I first did it, it auto generated quote marks around the numeric values that ive parameterized in my payload, but once I'd removed them it works fine

     

     

    have a look at the following screenshots:

     

     

    In the above screenshot you can see Im sourcing data from a csv using the Datasource (file) type.

    The first two values auto generate alpha numeric values, but column 3 includes a numeric and column 4 includes a string 1.0 is wrapped in quotes

     

    Next - if you look at the REST request in the screenshot below - in the Request tab and the payload editable field - you can see Im sourcing data from the Data Source test step.  

    if you look at the 'defraexp_ehcstatus' attribute value in the input payload above - the parameterized value is NOT wrapped in quotes (so it's numeric)

    If you look at the 'defraexp_ehcversion' attribute value in the input payload above - the parameterized value IS wrapped in quotes (so it's a string)

     

    Now - if you look at the next screenshot, you can see the RAW of the request - which shows what is submitted - in this case, the submitted payload maintained the attributes' datatypes relative to what was defined

     

     

    cool?

     

    Cheers,

     

    Rich

MFzOS's avatar
MFzOS
Occasional Contributor

Hello Rich and thanks for your response!

The thing is that I am not using groovy script when transferring data.

First I read data from excel file where I store the values in properties, then I use Property Transfer step to transfer these properties to fields in a JSON array. 

All values are transferred as string where some of the fields in the JSON are numeric. 

In the example below you can see the transfer step I use to transfer the value of the property "QUANTITY" to qty in JSON where the array will look :

{
   "data" : {
         "info" : {
               "qty" : "1750"
                    }
             }
}

 

Which is wrong because qty is numeric field and not string.

richie's avatar
richie
Community Hero
3 years ago
Hey MFzOS,

Ok. Weird....ive never seen someone bother using a property transfer step in between a Datasource step and a Request step before, cos you dont actually need to at all.....but you could teach me a new approach, so i need to just clarify!

Themore i think about this, the more confused i get and im starting to think im missing something essential.

am i understanding....you have a whole json payload in your datasource and youre using a property transfer to try and extract a numeric (which is part of the json payload), to then populate a specific attribute within a json payload that is hard coded into the editable field on your Request test step?

Reason why ive never seen it done the way i think youre doing is cos the functionality in the Request form can source values from your Datasource step directly (there is still property transfer taking place...you just havent got an explicit step in between your steps doing it).

For example...from what youve said it sounds like your testcase object hierarchy is as follows:

TestSuite
---TestCase
------Datasource step
------PropertyTransfer step
------RestRequest step

Whereas most people just do:

TestSuite
---TestCase
------Datasource step
------RestRequest step

The options im thinking of remove the hassle of you having to cast to numeric....its done as a consequence of your quote wrapping.

Ok...so....im typing this out on my phone right now, but when im infront of my laptop, i'll demo out your scenario using my approach and screenshot it all, so you can see clearly what i mean, but just to confirm a couple of questions:

Q1. Are you using Datasource type=file?

Q2. The source excel file youre using.....are you including the whole json payload in there

Q3. you have a whole json payload in your datasource and youre using a property transfer to try and extract a numeric (which is part of the json payload), to then populate a specific attribute within a json payload that is hard coded into the editable field on your Request test step?

Sorry...i know explaining repeatedly can be tedious, but if o dont understand completely, i'd probably give you the wrong answer....so its worth nailing the details down up front.

Cheers!

Rich
  • MFzOS's avatar
    MFzOS
    Occasional Contributor
    3 years ago

    Hello again! 

    First I want to thank for the effort you're putting to help me with this. I've been asking much lately about an easy way to cast a numeric value in a JSON attribute in ReadyAPI and I've not gotten the clear answer how to do that.

     

    Here comes the answers to your questions:

    A1. I'm using "Data Source Excel.xlsx".

     

    A2. In the same Data Source step one needs to create all the properties that correspond how the data looks in the columns in the excel sheet to be loaded and stored into when the Data Source step is being executed.


    A3.Yes, after all data has been fetched from the file.xlsx and stored in properties I use Property Transfer to distribute my data into JSON attributes for my REST request. I've tried both using Property Transfer way and assigning the data source direct for each attribute to be fetched from Data Source directly and in both ways my JSON request will automatically be populated correctly but all attributes are treated as text/string regardless if some of the attributes are numeric by definition or not.

     

    The attached picture I had in my previous comment shows the syntax that is being auto-generated when creating property transfer, neither that way or the auto-sourcing of data as you showed as  "${DataSource#attribute1" has an effect on how the attribute will look like in my JSON object. All attributes are handled as string/txt fields as I mentioned.

     

    I think there should be a way to choose or adjust to these auto-generated syntax when assigning actions to attributes that are being transferred that allow the user to choose if this will be casting numeric or sting type of attribute.

     

    Many thanks again for your help so far 🙂

     

    Regards,

    MFzOS

  • richie's avatar
    richie
    Community Hero
    3 years ago

    Hey MFzOS 

     

    if you can answer my latest questions - I can then get on with sorting what you need

     

    Cheers,

     

    Rich

    • MFzOS's avatar
      MFzOS
      Occasional Contributor
      3 years ago

      I'm not quite sure I got what you meant, but if you're referring to Q3, yes I get the JSON path expression hard coded when assigning values to be transferred from properties in the data source to the attribute in the JSON object in the request.

       

      Cheers!

      • richie's avatar
        richie
        Community Hero
        3 years ago
        Hey MFzOS,

        Sorry i read your previous message on my phone and didnt see the answers to the questions.

        Ive got my answers now. Yeah you dont need the explicit propTransfer.

        Im in meetings all day, but once it ticka over to 5:30pm, i'll add in my amswer, with screenshots how i do what you want.

        Cheers,

        Rich