is there any way we can add a custom field on the ...
# administration
e
is there any way we can add a custom field on the Customer record that would calculate average days to pay?
n
This could be a field sourced from Saved Search. First create your saved search which calculates your days to pay as a Summary field. Then use that search as the source for your field.
k
Just a heads up, this is a harder calculation than you think. Do you care about the last year? The last 5 invoices? All the way back to history? What happens with open invoices? Do they count? Just saying it's a challenging search to put together
If you have 30 invoices for a customer, an additional 1 doesn't change calculation all that much. It's one of those "oh that would be useful to know" that really isn't that useful from making decisions point of view
e
Thank you for the response. I am actually struggling more on how to set up the field than creating the saved search. I am unable to Group the average days by Customer in the saved search so how would i be able to filter it on the Customer record? Right now I have Custom Entity field; Type = Integer; Store Value = False; Search = (my saved search) Any suggestion is appreciated!
k
You'd do this as a transaction search - and you'd add an available filter of the customer internal ID
Your entity field type would be numeric, not integer
(unless you are rounding your search results)
your search would have1 result, just the average of your days to pay
e
I got all of those correct so far. Yes I am rounding my search result. And I only have 1 result, average of Days Open field. What should I enter in the 'Compare To' Field below the Saved Search drop down in Validation & Defaulting of the custom field set up? I have "Company" selected at the moment. Right now the custom field is blank in the Customer record...
k
it should use internal ID by default.
so you don't have to populate teh compare to field
Only reason to populate it is the field that gets pushed into the filter isn't the same as the internal ID of the current record
e
I see. Okay I think that worked. Thanks so much @KevinJ of Kansas!