General

Re: Calculations exceeded the maximum stack depth when use count(../preceding-sibling::my:Repeating_Table_Name)+1

jte71 — Mon, 20 May 2013 08:49:01 GMT

Hi Patrick,

Thanks for your response. The thing is, is that I imported an Excel sheet, and the format is a Form with a repeating table. When I run the Form, it gives me 31 (max day's of a month) rows with 3 columns, so I want the first column shows 1-31.

Kind regards,

Jurgen

Re: Calculations exceeded the maximum stack depth when use count(../preceding-sibling::my:Repeating_Table_Name)+1

Patrick Halstead — Sun, 19 May 2013 20:18:57 GMT

Hi Jurgen,

Why not just use default values and number them yourself to begin with. For new rows, you can have a rule on the repeating control that just sets your number column using the same formula. That way it only fires when a row is added and you get the first 31 (or whatever the default is) auto-numbered so you won't hit the browser issue.

I suspect that you are using a default value and some kind of insert logic to create 31 rows and that is what's causing the issue. By itself, the default value should not, but it's easy enough to just use default values - that's what they were intended for.

Good luck!

Calculations exceeded the maximum stack depth when use count(../preceding-sibling::my:Repeating_Table_Name)+1

jte71 — Sat, 18 May 2013 20:19:54 GMT

Hi all,

I use a repeating table in an Infopath form, and I want 31 rows when the form loads. In the Infopath Filler application it works perfect, but when I publish the form to SharePoint, and open the form in a browser I get the error Calculations exceeded the maximum stack depth when use count

Is it possible to get 31 rows without using count(../preceding-sibling::my:Repeating_Table_Name)+1

Kind regards,

Jurgen