CA Service Management

  • 1.  maileater issue with custom integer field

    Posted Oct 27, 2017 08:09 AM

    Hi,

     

    we are using CASD14.1 with C3 patch. we have one custom integer field ztest on incident page.

    when creating incident through maileater by giving %ztest=2320211748 the incident is getting created but the value of ztest in database is coming as -197475548.

     

    Do any one faced same problem or does any one know why the value is not populating properly



  • 2.  Re: maileater issue with custom integer field

    Broadcom Employee
    Posted Oct 27, 2017 08:24 AM

    Hello,

     

    A few questions:

     

    - Please describe how this field is defined in your custom schema, and in your maileater config (text_api.cfg)

     

    - What is the purpose of this field?  What kind of data is this field supposed to carry and contain?

     

    - Does the functionality work if you use a substantially smaller integer value?

     

    - Does the field value display correctly on the web interface?  You mentioned a value mismatch when you examined it from the database end.



  • 3.  Re: maileater issue with custom integer field

    Posted Oct 30, 2017 04:04 AM

    Hi David,

     

    Please find my reply for your questions:

     

    - Please describe how this field is defined in your custom schema, and in your maileater config (text_api.cfg)

     

    A)this field ztest is defined under Change Table as below:

     

    z_test INTEGER

     


    under maileater (text_api.cfg) it defined as
    CHANGE.Test=z_test.INTEGER

     

     

     

    - What is the purpose of this field?  What kind of data is this field supposed to carry and contain?

     

    A)The purpose of the filed is to capture the integer value.

     

     

     

    - Does the functionality work if you use a substantially smaller integer value?

     

    A) If I give smaller integer value its working fine

     

     

     

    - Does the field value display correctly on the web interface?  You mentioned a value mismatch when you examined it from the database end.

     

    A) The value is coming as -ve value both in web interface and database end



  • 4.  Re: maileater issue with custom integer field

    Posted Oct 30, 2017 08:44 AM

    Hi Subbarao,

    Thanks for responding to the questions.  In this case, as mitu mentioned, you are hitting the limit, thus its not accepting the value properly:

     

    Max value for an 32 bit integer is 2147483647, so your value of 2320211748 will overflow and produce an negative number, just as you noticed.

     

    Thanks,
    Jon 



  • 5.  Re: maileater issue with custom integer field

    Posted Oct 27, 2017 09:08 AM

    Hi Subbarao,

    Can you give us an idea on how you have this field set up in the schema?  Is this a field that is an SREL to another table (exiting one or a new one)?

    Give us an idea of the purpose of it and what you have it set to display on the incident detail form.

    Thanks,

    Jon I.



  • 6.  Re: maileater issue with custom integer field
    Best Answer

    Posted Oct 27, 2017 09:17 AM

    Max value for an 32 bit integer is 2147483647, so your value of 2320211748 will overflow and produce an negative number, just as you noticed.



  • 7.  Re: maileater issue with custom integer field

    Broadcom Employee
    Posted Oct 27, 2017 09:38 AM

    I was thinking that may have been the problem, the integer size limitation.  Still need an idea though of what this field is meant to do.  If the field isn't being used for any hard calculations, maybe change it over to a string data type?