Right, how does that effect it, by adding the letter Im pretty sure non of the date issue will happen, doesnt for me at least.
What comes after is irrelevent, its the - causing it, and whatever solution it wants to be applied accross the board so you can account for it consistantly else where, ie slicing first char of the value in print template if you need it bask to number without letter.
Thats good cause i dont understand you 
This is irrelevant if when it is a number with - it dosnt work.
Just try what I said to see if it resolves the issue, if not it doesnt matter anyway,
how i can write that what you said?
I already showed you;
this goes in the rule you showed here;
so i put an “A” in front?
Whatever you want, but a letter. It would need to be changed to a string field but should make it stay as a string rather than convert to a date base on that I have KAH-101 in an entity field without issue.
ok it works but the “A” show up to
Yer, thats expected. But your crash is resolved.
And you use this number where?
On receipts?
yes that should work like im expecting thank you!
yes im using it on printer template
OK, space will do same job I guess
Could try space on end.
Nope Space is not working causes an error for date calculation not in front and not in end
Ok, am lost.
Whats this?
Looks like you changed for a space?
yes y put there a space but its not working if i put only space there
I asked what that picture is.
You put space there where?
If A worked where is the A?
No i put there “RUCoCI=RUC/CI: [?RUC/CI]” and i tested it before that with “A[?RUC/CI]”
both worked like “RUC/CI: 123456-7” and “A123456-7”
but if i put there a space like this “RUCoCI= [?RUC/CI]” then causes an error in samba like before no matters in front or at end. "RUCoCI=[?RUC/CI] "
So the space in front worked?
only space no not works
Oh, ok, missed that you added the field name also infront.
So use the A and then use a script to slice the A off on print template if you need it to be removed for printing.
It will still show up in samba.