How to avoid zeros in orderlines (quantity, unit price and Amount) when using word as invoicereport

jsl_dk

When i make a commentline as an orderline (no itemno ) the order line looks fine.
But when i Invoice it and use word as report generator there are zeros in the line that doesn't look good. the report is 1306.
When i use the RDLC standard there are no problem regarding this issue.

mohana_cse06

you have to create a global variable with type text
add it in dataset below quantity field
you need to write code in proper place that if quantity = 0 then make the text variable ''
if quantity has a value the assign the value using format

jsl_dk

The platform is NAV2016 Release2
Thanks in advance

mohana_cse06

we have create text variables and made them '' if value 0 and used them in Quantity field.

Kappa

Thank you for your answer. Could you show which code you have changed?

mohana_cse06

Please try to implement it and let me know if you have any issues in implementing.

jsl_dk

Nice I will try it out

jsl_dk

jsl_dk

jsl_dk

It didn't help to try to make variables in the invoice form. As you can see there are no zeros in the form in NAV. they only appear in word as the invoice is printed?
Where do you put the code?

Belias

You have to create the variables in the REPORT, assign to them the formatted value of your decimal fields and convert them to '' if they are '0'.

jsl_dk

Thanks for your input.
How do you give the value ('') back to the quantity (decimal) to be outputted to word via XML?

jsl_dk

Or do you make the variable available to output?
How to do that?

mohana_cse06

you have to create a global variable with type text
add it in dataset below quantity field
you need to write code in proper place that if quantity = 0 then make the text variable ''
if quantity has a value the assign the value using format

Belias

As we wrote, you need a text variable to save the decimal value AS text.
Guiding you step by step to create a text variable in a report, then add it to the dataset(or the sections) and then to the report layout itself (and then debug the problems you are most probably going to have), will take us 100 posts.
A senior developer could do this in no time, if you ask him.