Grooper 21.00.0082 is available as of 12-12-2023! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 23.1.0016 is available as of 03-15-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 23.00.0042 is available as of 03-22-2024! Check the Downloads Discussion for the release notes and to get the latest version.
ParentInstance.DocumentInstance.Value in Grooper Attended Client.
hjanum
Posts: 110 ✭✭
I set up a table in my data model.
I need to do some character manipulation, so I need to look at values outside the table rows.
I configured an expression using the ParentInstance.DocumentInstance.Value.Length. It works well within Grooper Design Studio in 2.72.0028, but it does not work in the Grooper Attended Client.
Here is my debug field (Index).
Here is the expression:
Here is the result from within Grooper Design Studio when I test it there:
Here is the result from the Grooper Attended Client on the same document:
Note that the value of ParentInstance.DocumentInstance.Value.Length is zero and not 6002 as it is when called within Grooper Design Studio.
I need to do some character manipulation, so I need to look at values outside the table rows.
I configured an expression using the ParentInstance.DocumentInstance.Value.Length. It works well within Grooper Design Studio in 2.72.0028, but it does not work in the Grooper Attended Client.
Here is my debug field (Index).
Here is the expression:
Here is the result from within Grooper Design Studio when I test it there:
Here is the result from the Grooper Attended Client on the same document:
Note that the value of ParentInstance.DocumentInstance.Value.Length is zero and not 6002 as it is when called within Grooper Design Studio.
Tagged:
0
Answers
Solutions Manager
bgodwin@bisok.com
The issue occurs during extraction. The data is extracted by Grooper Design Studio during extraction testing in the data model looks correct, but when the data is extracted as part of a normal batch process then the value is wrong.
Are you able to reproduce the issue?