Given key [Dimension]-[Dimension field] was not present in dictionary

Question

Hello,I encountered an issue while opening the pivot table component that is connected to an OLAP engine. The pivot table is opened without any field in it.The error I get is the one in the subject of the thread, "Given key [Dimension]-[Dimension field] was not present in dictionary".I attach an example: in the .zip file you will find the screenshot with the error and the project that reproduces the error. (I took the screenshot directly from this project.)I am using the latest service pack, 18.4.0.39. Everything worked fine in the previous version I was using, 18.2.0.44.Thank you,RiccardoAttachment: PivotView_6bc41ae0.zip

Saranya Sivan · Answer

Hi Riccardo, 
  
Thanks for contacting Syncfusion support. 
  
We have checked the reported problem at our end. But we are unable to reproduce the problem. Meanwhile, we have prepared a video for your reference.  
  
Video Link: https://www.syncfusion.com/downloads/support/directtrac/general/7z/SYNCLAPN22584_2-2-2021_9.42.32_PM-602750932 
   
Note:  We suspect that the reported problem may occur when network speed is slow. So, kindly check your network speed. 
  
Regards, 
Saranya Sivan.

Riccardo Zucchetto · Answer

Hello Saranya,This morning I couldn't be able to reproduce the issue with the project I sent you, but I reproduced the problem in this project and in another one by connecting to a different OLAP source.It does not seem to be related to the network speed, since I tested it with two different networks and it happened with both of them.Can I ask you if, since the version I used before, there were changes in the request sent to the OLAP service (such as headers, parameters, etc)?Meanwhile I will try to reproduce it again and to send you the example.Thank you,Riccardo

Saranya Sivan · Answer

Hi Riccardo, 
Please find the response below,     
 




Query  

Response  


Can I ask you if, since the version I used before, there were changes in the request sent to the OLAP service (such as headers, parameters, etc)? 

No, we didn’t do such kind of changes in our updated version. 


 Meanwhile I will try to reproduce it again and to send you the example. 
  

Thanks, and we will wait until we hear from you. 
  
  
Regards, 
Saranya Sivan.

Riccardo Zucchetto · Answer

Hi Saranya,I have made more tests.The same issue re-appeared in other moments. I noticed it happens the first times I open it; then when it success to connect the problem never re-appears.I have tested it with different networks and I had the same issue, so it is not a network issue. Moreover, it happens also with the endpoint you provide for your example, which is not behind a VPN such as the one I use.Is there anything that I can try to let you debug the issue? Such as to provide a video or any other useful resource.Thank you,Riccardo

Saranya Sivan · Answer

Hi Riccardo,  
We have checked the reported problem thoroughly at our end. But we are unable to reproduce the problem. So, kindly share us your cube with dummy values or online link to connect the cube to reproduce the same at our end. This would be helpful for us to proceed further. 
 
Please let us know if you have concern. 
 
Regards, 
Saranya Sivan.

Query	Response
Can I ask you if, since the version I used before, there were changes in the request sent to the OLAP service (such as headers, parameters, etc)?	No, we didn’t do such kind of changes in our updated version.
Meanwhile I will try to reproduce it again and to send you the example.	Thanks, and we will wait until we hear from you.