Example: When leveraging Modeled Metrics within Reporting Tables which aggregate the current monthly Bill of IT by Application, the metric will return a NULL value (BLANK) if an Application dropped off the bill for a given month (assuming the use of perspectives to ensure the application field is configured to Show all row in time base query).

Issue: Because the Monthly Charges Metric can have a Negative Bill Amount in the case of a Billing Adjustment or Credit, when I sort on the Monthly Charges column in ascending order all the blank values for the Monthly Charge Modeled Metric show up on top when the desired view would place the largest Negative Charges on top. 

Work Around: Create a Calculated Metric with the formula =IF(LEN(Monthly Charges)=0),0,Monthly Charges)

Question for discussion: Should the system require this work around or should it automatically display the "disired" zero value (instead of blanks/nulls) ?

I also think it should be standard to return 0s, especially if it's on a billing report. I do understand why they return BLANKs as there is no data at all, but returning a 0 essentially says the same thing.

Maybe it could be an option on the table to return 0s for BLANK, in case some people do require the ability to see BLANK values to help with checking their model.

Zeros are neccessary rather than "Blanks" if the Modeled Metric is used in a calculated formulas. So in the case that the Model Metric is referenced within a Table formula or Calculated Metric it would be helpful to be "interpreted" as Zero.

I usually just multiply the value by 1...