Arithmetic Operation Resulted in overflow

[sapankumaarjain]

Hi Team,

I have created a simple report with 2 slicers but on selection if the values are beyond 3700 lines I am getting above mentioned error in the 2nd slicer. Its the latest version of Power BI Desktop.

Please advise @v-lili6-msft 

[amitchandak]

@sapankumaarjain ,"beyond 3700 lines" , not very clear. Can you explain it?

[sapankumaarjain]

Hi Amit,

I was checking the count as well based upon the selection so anything under 3700 rows was reflecting the values in the slicer. Beyond that its resulting in above mentioned error.

Regards,

Sapan

[v-rzhou-msft]

Hi @sapankumaarjain 

Could you show me your table and give me a screenshot of your issue?

This may make it easier for me to understand your issue.

Best Regards,

Rico Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly. 

[sapankumaarjain]

Hi Rico, 

You can see attached screenshot with error message thrown by slicer on selection of one purchase organisation. Also you can see the count is 6978. It shows data only if it is below 3700 rows. Its a simple dim table connected to fact.

Regards,

Sapan

[v-rzhou-msft]

Hi @sapankumaarjain 

Please show me your data source and your connection mode.

Can you sell all values in Slicer2 without any filter in Slicer1?

I have a test by geting data in Excel and using import mode.

My Sample table have two columns Level1 and Level2.

Level1 has three categorys A (2714 rows in Level2), B (7002 rows in Level2), C (200rows in Level2). 

When I select B in slicer1 (built by level1), slicer2 (built by Level2) works well.

And Desktop has upgrade, please update your desktop to the latest version (2.87.923.0 2020/11/25)

Best Regards,

Rico Zhou

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly. 

[sapankumaarjain]

Hi Rico,

Data Source is Snowflake in direct query mode. Without any selection in slicer 1 yes it shows data.

Meanwhile I will update and check once.

Regards,

Sapan

[sapankumaarjain]

Hi Rico,

In the updated version also I am getting same error. Also its not a numeric column.

Regards,

Sapan