Missing zero character bug?

Hi,

Would like know if anyone understand whats happening or any validation that i should do to get more information would be appreciated.

Bug cases:
- On the print1, on the execution log the name of the packages are missing zeros.
This packages and transformations:
             - 5_ Consulta_Corrigidos_Sem_Erro_Obrigatorio
             - 6_Consulta_Recusado_Inconformidade
Should be:
             - 05_ Consulta_Corrigidos_Sem_Erro_Obrigatorio
             - 06_Consulta_Recusado_Inconformidade
This kind of bug seems to not have a real affect on the execution of the Package, but in other cases its worst.


- This missing zero bug happens in variables too. On prints 2, 3 and 4 i have a literal variable with the value "2100-12-31", and during execution it changes to "21-12-31", missing all zeros.


INFOS:
- As the print5 shows we are at version 6.4.5.14, but we also tried versions 6.4.5.14, 6.4.5.13 and 6.4.5.12.

That look very unusual, I have never seen anything like this before. 

We will try to reproduce it in the office.

I isolated the problem, now i have the transformation with the bug attached as txt file.
The problem only happens when the lookup called BUG inside the transformer BUG_LOOKUP is connected, if i use the sql lookup called WORKING this kind of bug does not happen.

On print21 i show the transformation with the transformer that the bug happens.
On print22 i show the bugged lookup and the working lookup.
On print23 i show the package running with the working lookup.
On print24 i show the package running with the bugged lookup, that delete all the 0s.

Looking at it now

May I suggest not use underscores in object names.

This will make designing packages much easier.


 

Ok, understood.

1 We have reproduced the issue with incorrect description in the log. this will be addressed in the next release.

2 Regarding failing lookup. Can you check for variable called '0'

It can be the source of the problem