Select to view content in your preferred language

Invalid Calculate for the bind... error

744
6
Jump to solution
01-22-2026 05:49 AM
GaryBowles1
Frequent Contributor

I am trying to count records in a repeat and display the count outside of the repeat. I have one calculation and display that is working fine but I am receiving an error for the 2nd and 3rd calculations. I have attached screen grabs of the xlsx form and the error in Connect. The Esri::bind field is set to int. Any help is appreciated.

Thanks,

--gary

0 Kudos
1 Solution

Accepted Solutions
Neal_t_k
MVP Regular Contributor

@GaryBowles1 In the screenshot, you attached to your original you are missing a "{" in your sum calculation. 

Neal_t_k_0-1769094523474.png

Edit: Also in the ones above you have "(" instead of "{"

 

View solution in original post

6 Replies
Neal_t_k
MVP Regular Contributor

Try setting the bind:type to int.

That should work, but you can always call it a number in the calculation if it doesn't for some reason: sum(number(${countstepscomplete}))

edit:

Neal_t_k_0-1769093618337.png

 

0 Kudos
GaryBowles1
Frequent Contributor

The bind::type is set to int. I tried the sum(number($(countstepscomplete})) and sum(int($(countstepscomplete})) still not love.

thanks,

--gary

0 Kudos
Neal_t_k
MVP Regular Contributor

@GaryBowles1 In the screenshot, you attached to your original you are missing a "{" in your sum calculation. 

Neal_t_k_0-1769094523474.png

Edit: Also in the ones above you have "(" instead of "{"

 

GaryBowles1
Frequent Contributor

Can't see the forest for the trees. You stare at something that you think should work and can't find the simplest error. That solved the problem. Much appreciated.

--gary

ZenMasterZeke
Frequent Contributor

Not exactly sure of everything you're looking for here, but the problem is likely in just the first calculation, which affects the second. Don't have time right now to look deeper into it, but it's probably where you try to convert a date to string. Dates behind the scene are stored as long numbers, either the seconds or minutes past a certain date, such as 01-01-1900. They're then (hopefully) formatted to display a certain way.

0 Kudos
GaryBowles1
Frequent Contributor

I agree that the error is probably with the original calculation which is:

if(string-length(string(${p_stependdate})) > 0, 1, 0)

From what I have been able to find in the documentation, this should grab the date, convert to string, and check if the string length is greater than 0 and return 1 for yes and 0 for no. Am I missing something in the above calc?

thanks,

--gary

0 Kudos