[file]10233[/file] - it was noticed that sometimes the order amount from the variable pulls with thousandths in the format 123.0000 instead of 123 , this leads to sending 2 sms instead of 1 and often customers do not correctly understand the amount.
- it was noticed that sometimes the order amount from the variable pulls with thousandths in the format 123.0000 instead of 123 , this leads to sending 2 sms instead of 1 and often customers do not correctly understand the amount.
You can specify the number of digits after komi in square arms in the middle of the change, for example {|$ordersum[#0]|} - means that the number of the "sum of the process" will be rounded to tsіlih
You can specify the number of digits after komi in square arms in the middle of the change, for example {|$ordersum[#0]|} - means that the number of the "sum of the process" will be rounded to tsіlih
Yarina integrator wrote: You can specify the number of digits after komi in square arms in the middle of the change, for example {|$ordersum[#0]|} - means that the number of the "sum of the process" will be rounded to tsіlih
Dyakuyu! I'm just wondering why in 90% of cases the system generates a round sum, and in 10% it prescribes a comma and zeros. didn't see the pattern.
[quote]
Yarina
integrator wrote:
You can specify the number of digits after komi in square arms in the middle of the change, for example {|$ordersum[#0]|} - means that the number of the "sum of the process" will be rounded to tsіlih
[/quote]
Dyakuyu! I'm just wondering why in 90% of cases the system generates a round sum, and in 10% it prescribes a comma and zeros. didn't see the pattern.
and another problem is that {|$ordersum[#0]|} is formed only in the data array, and separately the [ordersum] variable behaves differently for some reason
and another problem is that {|$ordersum[#0]|} is formed only in the data array, and separately the [ordersum] variable behaves differently for some reason
Zubarev Sergey Optium Client wrote: Dyakuyu! I'm just wondering why in 90% of cases the system generates a round sum, and in 10% it prescribes a comma and zeros. didn't see the pattern.
here, perhaps, the programmers can give advice.
Zubarev Sergey Optium Client wrote: and another problem is that {|$ordersum[#0]|} is formed only in the data array, and separately the [ordersum] variable behaves differently for some reason
because of the different types of change. the curly temples are exactly right.
[quote]
Zubarev Sergey
Optium
Client wrote:
Dyakuyu! I'm just wondering why in 90% of cases the system generates a round sum, and in 10% it prescribes a comma and zeros. didn't see the pattern.
[/quote]
here, perhaps, the programmers can give advice.
[quote]
Zubarev Sergey
Optium
Client wrote:
and another problem is that {|$ordersum[#0]|} is formed only in the data array, and separately the [ordersum] variable behaves differently for some reason
[/quote]
because of the different types of change. the curly temples are exactly right.
no output of {|$ordersum[#0]|} variable in sms caused process to crash - this variable does not work in sms , reverted to [ordersum]. but it is still not clear why in the same stages of the process the variable is formed differently.
no output of {|$ordersum[#0]|} variable in sms caused process to crash - this variable does not work in sms , reverted to [ordersum]. but it is still not clear why in the same stages of the process the variable is formed differently.
no output of {|$ordersum[#0]|} variable in sms caused process to crash - this variable does not work in sms , reverted to [ordersum]. but it is still not clear why in the same stages of the process the variable is formed differently.
in Smarty, you can use the number_format modifier, which sets the format for displaying the date you can try the variable {|$ordersum|number_format:0|} (this is if rounded to integers), or {|$ordersum|number_format:2:".":","|} (2 decimal places, decimal separated by a dot, and thousands - a comma)
[quote]
no output of {|$ordersum[#0]|} variable in sms caused process to crash - this variable does not work in sms , reverted to [ordersum]. but it is still not clear why in the same stages of the process the variable is formed differently.
[/quote]
in Smarty, you can use the number_format modifier, which sets the format for displaying the date
you can try the variable {|$ordersum|number_format:0|} (this is if rounded to integers), or {|$ordersum|number_format:2:".":","|} (2 decimal places, decimal separated by a dot, and thousands - a comma)
Tyndyk Maxim Vadimovich OneBox production Administrator wrote:
no output of {|$ordersum[#0]|} variable in sms caused process to crash - this variable does not work in sms , reverted to [ordersum]. but it is still not clear why in the same stages of the process the variable is formed differently.
in Smarty, you can use the number_format modifier, which sets the format for displaying the date you can try the variable {|$ordersum|number_format:0|} (this is if rounded to integers), or {|$ordersum|number_format:2:".":","|} (2 decimal places, decimal separated by a dot, and thousands - a comma)
your solution is working, thanks.
[quote]
Tyndyk Maxim Vadimovich
OneBox production
Administrator wrote:
[quote]
no output of {|$ordersum[#0]|} variable in sms caused process to crash - this variable does not work in sms , reverted to [ordersum]. but it is still not clear why in the same stages of the process the variable is formed differently.
[/quote]
in Smarty, you can use the number_format modifier, which sets the format for displaying the date
you can try the variable {|$ordersum|number_format:0|} (this is if rounded to integers), or {|$ordersum|number_format:2:".":","|} (2 decimal places, decimal separated by a dot, and thousands - a comma)
[/quote]
your solution is working, thanks.
Please join the conversation. If you have something to say - please write a comment. You will need a mobile phone and an SMS code for identification to enter.
Log in and comment
Donate
You don't have enough funds in your account Top up