Function evaluation is disabled because a previous function evaluation timed out

[Suranga R]

Hi,

I have a complex calculation one of my excel.

This is how excel organized in short...

Sheet2 => There 6 column row and each cell has a formula. Then I have dragged this 6 cells row up to 10000 rows so each row has a repeated formula.

Sheet1 => There is cell (Ex: A1) value and depending on the value Sheet2's above mentioned rows getting evaluated

Sheet3 => Similar logic as Sheet2

Sheet2 => There are couple of columns which does VLOOKUP from Sheet3 aa,d Sheet3 has similar VLOOKUP from another Sheet such as Sheet2/Sheet3

Input   => Sheet1:A1 = Number

Output => Sheet1:A2 = VLOOKUP from Sheet2's above mention 6col x 10000rows area

This is a complex recursive evaluation and sometimes you might see it is redundant (But it is not because of the logic behind it, but sure there might be a better way)

When I try to get Sheet1["A2"].CalculatedValue, return #NA after 2,3 minutes.

If I tried Sheet1["A2"] in the Watch area in the VS debugger, it dumps "Function evaluation is disabled because a previous function evaluation timed out" message.

I really sure this very complex to solve in a regular programming model.  But I would except at least "too complex" message if there are more than 100 (default) recursive calls, but what it returns is "#NA".

My questions are,

1. Is there a way to debug XlsIO so I can find out where it is getting failed

2. Is there any advice you can give me (I'm OK to drop this evaluation since it is too complex, but #NA value is not something I can go with, I need to find a better reason why it is failing..etc)

3. Are there limitations with the above scenario?

Essential Studio 15.3.0.26

Note: Works with MS Excel 2013, but there is a 3,4 seconds delay sometimes.

Thank you very much!

[Abirami Varadharajan]

Hi Suranga, 

 

Thank you for contacting Syncfusion support. 

 

Based on the given details, we have tried to replicate the reported issue with different scenarios at our end. But unfortunately, we are unable to replicate the issue. So, we suggest you to share any sample or video link with clear replication procedure which would highly help us to analyze the requirement better and update you an appropriate solution. Please find the details for your queries below. 

 

Queries	Details
Is there a way to debug XlsIO so I can find out where it is getting failed	No, you can’t debug XlsIO unless you have an source code license.
Is there any advice you can give me (I'm OK to drop this evaluation since it is too complex, but #NA value is not something I can go with, I need to find a better reason why it is failing..etc)	This is only document specific and might occur due to formula redundancy.     As we couldn’t reproduce the issue from side, we couldn’t provide solution for this issue.   Please provide the issue reproducing sample which will be helpful for us to provide prompt solution.
Are there limitations with the above scenario?	No, there is no limitation.

 

Regards, 

Abirami. 

[Suranga R]

Hi Abirami,

Thank you very much for the reply.

I will share a sample sheet within a week. I'm pretty sure there is something going on with the way we (i.e. excel author) use formula in the excel.

Thanks,

Suranga

[Prakash Kumar D]

Hi Suranga, 

  

Thank you for updating us.  Please provide a sample sheet to proceed further. 

  

Regards, 

Prakash Kumar 

[Suranga R]

Hi Prakash,

Is there a way to share an excel with your team confidentially?

Because I'm not allowed to drop it in a public area, but if you have a secured channel that I can share it with you, please let me know.

Or else I have to duplicate the problem in another excel sheet and that could take more time or it may not even possible to duplicate it.

Appreciate your help very much on this.

Suranga.

[Prakash Kumar D]

Hi Suranga, 

 

Yes, you can share the document by creating an incident through the below link  

 https://www.syncfusion.com/account/login 

Note: As per Syncfusion norms, the provided documents are used only for testing purpose and we will maintain it confidentially. 

Regards, 

Prakash Kumar