All ideas are welcome. Just because the Idea doesn't make it into the product immediately does not make it a bad idea.
An example I have is a price column which is a text box showing the final price (sum of list and discounts) of an audit in the header page of a header detail layout this field's value is linked to the child pane where the individual pricing lines exist. If there are not yet any pricing lines I am displaying "NA" in as the price in the header so that I have a value to link on. I would use 0 but sometimes 0 is a valid price and I must distinguish between 0 and NULL. I also have the numeric column property on my price field in the header so that I can have it display as currency, limit the decimal places, and display the thousands separator. It is great that this works for numbers even though some of the fields display 'NA' an not a number. Unfortunately the Sum attribute does not work because it hits a data type issue with the 'NA' fields.
Jeremiah Gilmore
Thanks for logging this idea. We will put this into the backlog for consideration and ranking against the other framework related items. I think the logic is sound to make this exclusion / handling capability and as we only support the ability to calculate Sum (total) in the framework this should be a fairly straightforward fix.
Attachments Open full size