Data stream is working fine in flow designer but data source is not working

[Sunil25]

Hello Experts,

I have created a data stream action in flow designer for REST integration and able to pull the data. This is tested with Test functionality in Flow designer. Now data stream is added to data source and when i click on "Test Load 20 records", it is working fine and able to see the 20 rows/records in loaded data. But when i am trying to click on "Load all records", it is loading some records(i can see the count when progress worker is loading) and then it is throwing an error.

Error: com.glide.transform.transformer.exceptions.InvalidPathException: Could not find path in stream: $.value

The sample JSON data i am trying to pull as below.

{"@odata.context":"windows","value":[{"computerDnsName":"064206305d","osPlatform":"Windows10","osVersion":null,"osArchitecture":"64-bit","vmMetadata":null}]}

I put $.value in "item path" of data stream action.

I gave computerDnsName, osPlatform, osVersion and osArchitecture as outputs.

I am able to see the data when i click on 'Test' in flow designer. it is working fine while test load of 20 records in data source, but error during load of all records. 

Please suggest if I am missing something here.

Thanks,

Sunil Safare

[Sunil25 · Accepted solution]

This issue is solved when I removed "Enable pagination" option. I am not sure of reason, but posting here, it may help others.

Thanks,

Sunil Safare

[AlekhyaD2093158]

Hi, can you tell me how did you removed enable pagination. when am trying to do it is disabled. Is it like we have to copy action and add the copied action to flow ?

[Jack38]

For anyone who sees this in the future, removing the "Enable pagination" is a bandaid fix and does not address the issue at hand.

Whenever you see the "com.glide.transform.transformer.exceptions.InvalidPathException: Could not find path in stream: $.value" exception from the Splitter step of the Data Stream action, this indicates that the REST step's response body does not contain the expected item path ($.value in this case). This can be due to any number of reasons, but is usually is due to one of the following:

1. misconfigured credentials that results in a 401 or 403 error
2. misconfigured pagination configuration step which results in some 4xx code

In either case, what usually happens is that the response body contains a completely different JSON structure than  expected.

Likely what happened here is that OP's pagination configuration was incorrectly misconfigured which resulted in an unexpected response in the REST step. The easiest way to verify what's wrong is to:

1. Test run your Data Stream action (with and without pagination enabled)
2. Open the Operations View of the flow context and make sure the REST step's Response Status and Response Body are expected in each case.

Example screenshot below shows issue caused by a 401 Unauthorized error from REST step.