Beroepskosten 2.0 - default accounts with categories

@Cedric,

It’s this statement that decides whether or not the export will display the accounts.

Your ifi-statement is looking at the object custom.anderebo.accounts but that object will be empty by default, even if you use a default-account range!
That object will not be empty or blank, when you actually press the button # and drag some accounts in it.

It’s a very wierd thing to work with an input-tag and a default-value to it. You can clearly see the behaviour, if you do this :

{{ custom.anderebo.accounts }}

It won’t show anything.
However, if you press the # and drag an account in it, you’ll see what happens: the object now does have a value.

Why? An input-object will only have actual data in the object, only if you actualle put in data in there.
The default-value added to it, is only some sort of a layer over the object (to show in input and export mode), but it doesn’t actually input the value in the object.

I’ll admit, strange in the beginning but I have explicitly documented this in the slides of the workshops.

To get back to a solution:

You have a collection that stores all the accounts, so why not do a check on the collection anderebo?

For instance :

{% ifi anderebo != empty %}
{{ detailanderebo }}
<br>{% endifi %}

or

{% ifi anderebo.value != 0 %}
{{ detailanderebo }}
<br>{% endifi %}

Could you give it a go ?

Nice looking template by the way :+1: