[Isomorphic]

Why does the second request have criteria? Are you setting it, or is being done automatically by CubeGrid?

[b.kazybaev]

I did not setting it. It is being done automatically by CubeGrid.

[b.kazybaev]

When I open chart the framework do not create Criteria in request so the rest data loads.

{
    dataSource:"UserCubesEvaluation", 
    operationType:"fetch", 
    data:{
    }, 
    showPrompt:true, 
    requestId:"UserCubesEvaluation$6273", 
    fallbackToEval:false, 
    bypassCache:true
}

[b.kazybaev]

Hey, Isomorphic

I am still waiting for your answer regarding my issue.

[Isomorphic]

We're not able to reproduce any kind of general problem using CubeGrid and a cacheAllData:true DataSource. You can enable this property in samples and see that everything works as expected.

The only explanation we can find for partial data would be that you perhaps have an event handler that is firing when the first batch of data arrives, and that event handler crashes, ending further processing. So check the Developer Console for warnings or stack traces of JavaScript errors, as well as native browser developer tools (hit f12).

[b.kazybaev]

Thank you for explanation.

Yes, I have an event handler but it fires when "onCellClick" event in advancedcube occurs. I checked the Developer Console for warning of JavaScript errors and did not find anything.

I can not understand why after first request the second request generates with criteria.

I mentioned about it in previous answers:

1) in RPC tab
There are two requests. The first one's URL is:
http://127.0.0.1:8888/cubegrid/sc/IDACall

The second one's URL is:
[client only]

Could you explain me such behavior of CubeGrid? Any ideas how to resolve this issue?

[Isomorphic]

The requests and responses you see in the RPC tab are normal. Again, you can see the same the behavior, with correct results, if you switch the CubeGrid samples in the SDK to use cacheAllData:true.

The first request is an actual request to the server to retrieve all available rows.

The second request is a fetch from the CubeGrid against the DataSource to retrieve specific rows it needs to display. It is marked [client only] because it gets resolved from the cache.

It's also normal that this request would contain criteria. In the Advanced Cube sample, you can see that filling the initially visible area of the cube takes multiple requests with different criteria.

To look further, we need some way to reproduce this problem.