resource efficient way to use of variables that depend upon each other that refer to long JSON paths

RE: resource efficient way to use of variables that depend upon each other that refer to long JSON paths

erikb0001 — Thu, 26 Aug 2021 12:20:57 GMT

Thank you Stefan, I will keep that in mind.

RE: resource efficient way to use of variables that depend upon each other that refer to long JSON paths

Stefan Helzle — Thu, 26 Aug 2021 12:19:52 GMT

index() will help you to catch the case that field does not exist at all. If you know that all the fields are always available, just go with the dot-notation.

RE: resource efficient way to use of variables that depend upon each other that refer to long JSON paths

erikb0001 — Thu, 26 Aug 2021 11:23:35 GMT

Thanks Stefan,

Your assumption is right, the values will be used in a CDT.
I started with separate variable's to individually check the responses fist, also for the majority of fields I also have to "filter" using for each to get the right value(s) out of the array. Now that I am able to correctly fetch the data along with your answer to my question, I will indeed initialize the CDT with the values by dot notation full path for each field in the CDT and then wrap them like this to handle null values.

companyEmail: index(local!totalRespons.result.body.serverInfo.company.contactInfo.item"email", null),

Or is this not a good thing to do?

Kind Regards,

Erik

RE: resource efficient way to use of variables that depend upon each other that refer to long JSON paths

Stefan Helzle — Thu, 26 Aug 2021 10:53:46 GMT

I think that multiple lines like

local!companyEmail: local!totalRespons.result.body.serverInfo.company.contactInfo.item.email

are super readable.

What do you then do with these values? Why create a local for each? I assume you want to transfer them into your own CDT. Then you can do this

type!YourCDT(
  companyEmail: local!totalRespons.result.body.serverInfo.company.contactInfo.item.email,
  .
  .
  .
)