On Fri, Aug 30, 2013 at 02:09:16PM -0700, Landon Stewart wrote:
On 29 August 2013 13:31, Kevin Falcone [1]falc...@bestpractical.com
wrote:
Because Custom Fields can hold a LONGBLOB worth of data.
Go save a large text CF and look in the database.
Saving them as 1000
On 29 August 2013 13:31, Kevin Falcone falc...@bestpractical.com wrote:
Because Custom Fields can hold a LONGBLOB worth of data.
Go save a large text CF and look in the database.
Saving them as 1000 individual values makes 1000 records in the
database, saving them as 1 large record makes 1
On 30 August 2013 14:29, Kevin Falcone falc...@bestpractical.com wrote:
If you have a multiple value custom field, then each value will be an
OCFV.
As I wrote above Go save a large *text* CF and look in the database
(added emphasis on text).
It's unclear to me how you think we could store a
On Tue, Aug 27, 2013 at 09:36:53AM -0700, Landon Stewart wrote:
On 27 August 2013 09:27, Kevin Falcone [1]falc...@bestpractical.com
wrote:
It'd be safer to use the RecordTransaction argument to
AddCustomFieldValue which tells RT whether or not to record a
transaction.
On 2013-08-26 21:55, Landon Stewart wrote:
For example if there are 1000 IP addresses in a ticket and there are 4
custom fields to be updated it creates 4000 transactions for that one
ticket when looping each update individually.
What I'm wondering is if there's a better way to make these
On Tue, Aug 27, 2013 at 09:51:57AM +0100, G. Dawson wrote:
On 2013-08-26 21:55, Landon Stewart wrote:
For example if there are 1000 IP addresses in a ticket and there are 4
custom fields to be updated it creates 4000 transactions for that one
ticket when looping each update individually.
On 27 August 2013 09:27, Kevin Falcone falc...@bestpractical.com wrote:
It'd be safer to use the RecordTransaction argument to
AddCustomFieldValue which tells RT whether or not to record a
transaction.
This avoids the problem of directly manipulating OCFVs and potentially
truncating them
Hello,
Currently we are utilizing some internal systems to lookup the Customer ID
and other data related to that customer to add to Incident Reports coming
into RT. Some organizations include a list of IP addresses or URLs related
to a specific type of Incident. Those IP addresses or URLs might