Response Mapping

[mbarfiel]

I have been working on this block map for some time and I can't identify the error. The step issues give me a descriptive message but I have a hard time deciphering the messages. There may be a trick to identifying the issues quickly I will read the help and FAQs to see if there are tips on debugging response maps - especially block maps.

In the short term can you identify what I'm doing wrong with this one.

The last sample has double digit slot values and that may be throwing it off. I modified the previous samples to use double digits and the maps seemed to work OK. The last response has an issue that isn't jumping out.

Also, I'm open to creating another block map if I can't get this one to work. I think the changes are minor enough that it should work k on with this existing map.

I would appreciate some expert help on this.

Thanks in advance.

[YujieL]

the reason you get mapping error on the last sample is that on the third row  of your last sample (which is the first data row), it ends with a space followed by a comma:

15/1  PAIRWISET11_NV838_1  4000   4000   1      15/1 ,15/2 ,15/3 ,15/4 ,

In your block map definition, the comma is optional, but it doesn't specify that there can be a space followed by a comma.  If you remove the space, then that line starts mapping.

The errors in the step issues view are not intuitive.

Since your samples only consist of tables. Have you considered using a table map instead?

[mbarfiel]

Thanks for pointing out the comma issue. I think that created more questions than answers. Unfortunately, the misplace comma in the response is the actual output of the CLI. I tried to make the space optional but that created additional mapping errors. The comma problem is in the first row only so that is creating a challenge with the response map.

How do I deal with the extra space? Also, I tried using a table map but I'm not sure how to deal with the extra rows due to the links. The response can contain 1 to 8 links. I'm open to suggestions but I need to deal with the messed up output.

Example output rows 1(extra space before comma), 2, and 3:

...15/1 ,

...16/5,

...17/10,

[PaulD · Accepted solution]

I'm attaching an updated map.  I believe you just failed to add optional spaces after each token in the second row of the body block.  Seems to work now on all of your samples.

[mbarfiel]

Paul, you nailed the issue. I wasn't accounting for the optional  space. The CLI response placed a space before the comma if the port was a single digit value and no space after double digit values.

These issues require a good attention to detail and I appreciate you guys helping me point out the obvious.

Thanks.

[PaulD]

My pleasure.  Indeed, block mapping can be tricky and requires a good eye for detail.  We're constantly looking for creative ways in which we can make it easier and/or more forgiving.  If you have any ideas, we'd love to hear them.