Custom Values: nested, fallback, ability to blank, field types, validation
C
Clifford Paulick
NESTED:
ability to have custom values used within a custom value, such as for concatenation
FALLBACK:
Example: {{custom_values.phone_number_for_display:fallback="(111) 222-3333"}}
ABILITY TO BLANK:
If I have fallback functionality, it makes sense to allow blank values. They're already allowed upon initial Snapshot import anyway. Why not allow resetting to blank whenever I want?
FIELD TYPES:
(Custom Fields already has multiple field types.)
- Link
- color picker
- Media picker (saves the URL value of the chosen/uploaded media item)
- WYSIWYG (saves the HTML value)
- Code Editor
VALIDATION:
- trim
- no spaces
- minimum length
- maximum length
- string must include (e.g. 'facebook.com')
- email address
- regex
C
Clifford Paulick
ABILITY TO OUTPUT WITH MODIFIERS:
Like https://docs.gravityforms.com/field-merge-tags/#h-modifiers
Example:
:numeric
Converts the number string or currency value as a decimal-formatted number.
K
Keith Besherse
Clifford Paulick, is there a reason you don't have Field Types: Numeric, Date, and Monetary?
C
Clifford Paulick
Keith Besherse Wouldn't you just manually type those in as plain text? I suppose a datepicker field would be interesting instead of having to cast toDate() if such a thing exists in Workflow logic.
K
Keith Besherse
We shouldn't need to do this work around: https://youtu.be/M-eRoaEOruc?si=m5NRGWT3ZQCtswa-
K
Keith Besherse
Doing Math Operations with Custom Values is currently possible.
Doing Math Operations ON Custom Values is not.
Should also apply to Opportunity Custom Fields!
C
Clifford Paulick
Keith Besherse try just pasting
{{invoice.total_amount}}
into Lead Value field (even though it's not in the dropdown selection options)C
Clifford Paulick
Keith Besherse well this Idea won't let me edit this far after posting so hopefully GHL Staff will know the right way to proceed with a fully thought out solution
K
Keith Besherse
Clifford Paulick, Thank you!
The issue at the individual Contact level comes when you want to use the existing Lead Value field value as a cumulative lifetime value of the customer. You cannot add current Invoice Total Amount to Lead Value. You have to create a separate Custom Field to use as a buffer. Then Update Opportunity Lead Value with that buffer.
But that is not the use case which led me to engage with your suggestion.
My concern is with alternate types of Custom Value which apply at the sub-account (location) level, not only the individual Contact level. Right now, we only have only text-type Custom Values. You have asked for link, color picker, WYSIWYG, etc. I am asking that we also ask for Numeric, Date, and Monetary. When something happens with a particular Contact (or Opportunity) in a Workflow it sometimes affects something at the sub-account (business/company/location) level.
Here is an example:
There are X slots available. Each time an order is submitted, we want to show the number remaining on the landing page.
Right now, we have to pull the account-level Custom Value into a Contact-level buffer, use a Math Operation on the buffer Custom Field, then use the Update Custom Value to insert the text value back into the Custom Value.
If we had numeric-type Custom Values (and Math Operations could reference Custom Values) we would have a one-step action to subtract 1 from the slots available Custom Value.
The workaround is not onerous. But it would be unnecessary if we had numeric-type Custom Values.
Adam McInnes , Shaun Clark , Varun Vairavan , Brendan Barth
C
Clifford Paulick
Combine votes with these others (mostly focused on 'fallback' but not mentioning the additional functionality I requested in this request:
A
Aharon Zagury
very much needed, especially validation