I created a shared header like the one show in this topic CASE: make header with additional info in a recon template where I use custom checkboxes (boolean) and also show the info about who and when someone have used the checkboxes by using the updated_by.name and updated_at code for the custom fields.
The problem is when I do a rollforward the checkboxes should be cleared and this doesn’t happen. They stay on true (or false) even when I add the rollforward nil to the checkboxes. I have put this rollforward code in the shared part but also in the actual template that use this shared-part.
The only thing that happens is that the date and person is updated. I’ve used the code “rollforward false custom.prepared.check” or “rollforward nil custom.prepared.check” , but both doesn’t work.
Is there a solutions to make sure that the checkboxes are always cleared when they are copied to a other period?
After taking a look at your code, the second block of code sent over and the “nil” approach to the rollforward is correct, however the first segment of code you sent over can be updated, the case you sent over previously does not factor in rollforward, which could be the reason why this isn’t working as expected.
To ensure that the “updated_by.name” and “updated_at” is not displayed when the template is rollforward, if check should be added.
In this example check “custom.prepared.check == true” is added:
Thanks for taking a look at it.
So, you mean that I should remove the rollforward code in the shared header part (first code) completely?
I think that it works now, probally the problem because the previous period where I wanted to copy from, has a slightly other shared header with only 2 custom booleans (where the period has been locked, so the template doesn’t update anymore) , and were I now have 3 custom booleans. Even when the first 2 custom booleans are the same as the old one, this doesn’t work. I have tried to copy from an open period and then the rollforward does a correct job.
Just a qeustion: the rollforward code has to be only in the final templates, correct? Or could I put it (only once) in the shared header. If not than I have to adapt all other templates that uses this header.