Storing Error Data
Hi Team, i am reading csv file and calling API with rest get snap by adding parameter to URL dynamically which is coming form csv file. so now i want to store data into file form csv ...
Forum Discussion
If you have the liberty to restructure your test.expr expression library file, I would recommend moving to the match control operator syntax for reduced code and simpler reference. For the test.expr file, you could change it to:
{
"main": cm => match cm {
"T" => "",
"100000" => "9999",
"200000" => "",
_ => ""
}
}
After, you can use a simpler reference:
lib.test.main($CM)
However, if you can’t make a major change to the structure for some reason, but can adapt it to an arrow function, you can incorporate bojanvelevski’s suggestion in the expression library and still use the simpler lib.test.main($CM) reference. The file might look something like this:
{
"main": (cm =>
[
{
"CM": "T",
"TM": ""
},
{
"CM": "100000",
"TM": "9999"
},
{
"CM": "200000",
"TM": ""
}
].filter(x=> x.CM==cm)[0].TM)
}
There are other restructuring options, as well.
Tried this. Worked for me. Thank you so much!
In similar scenarios when the endpoint does not return the necessary info to determine the the ‘next page’ request directly I have used
snap.in.totalCountI think in your scenario, the value returned by the above multiplied by the _pageSize pipeline parameter would equate to the Offest value you require for the next ‘next page’ request.
Matt.
Hi Matt,
thank you very much, I couldn’t solve it with
snap.in.totalCount, butsnap.out.totalCountdid the trick.For people searching this in the future, here is the configuration. Specifically this is used with the Workday REST API.
Best regards
Thomas
