Hi @Katrien,
I’m assuming you’d like to get to the completion of a reconciliation template, right? To see if it’s reconciled, or not, no?
If so, it is not possible to link to the reconcile-status of a template like you’d refer to a database variable.
However, you could use a workaround by having the variables that define your reconcile-status, taken into a result-tag.
For example:
Let’s take the code of this case:
I’ll add this code within the forloop, just when the local variable check_ind was created :
| {% input custom.[check].check_mark as:boolean %}
{% comment %}Below will make the templates reconciliation needed{% endcomment %}
{% if custom.[check].check_mark == true %}
{% assign check_ind = 0 %}
{% else %}
{% assign check_ind = 1 %}
{% endif %}
{% comment %}add the value of the ind var into a register{% endcomment %}
{% assign $10 = check_ind %}
| {% unexplained check_ind as:indicator %}
The part that’s added here, is:
{% assign $10 = check_ind %}
So each loop, the value of the local var is added into $10. If all checks are done, that value of $10 should be zero.
At the end of the code, we can do this, and combine all variables that decide the reconciled status of the template:
{% comment %}we need to take the reconciled variables into a result tag so we can refer to from somewhere else{% endcomment %}
{% assign recon_status = check_prep+check_review+$10 %}
{% result 'status_checklist_a' recon_status %}
You can then refer to that result tag to see if a template is reconciled or not. If the value of the result tag is zero, it’s reconciled. If it’s not zero, it is unreconciled.
But yes, you have to add additional code for that.
Can you let me know if this works out for you? Great case Katrien!