This topic contains 4 replies, has 0 voices, and was last updated by mark petzold 16 years, 10 months ago.

  • Author
    Posts
  • #8600

    mark petzold

    I’m trying to add the category field from the customer table on a Crystal report but category does not appear in my view. According to the help documentation it should be in the customer table, but it isn’t. I’ve refreshed the view and all our recent cutom fields are there, but category is MIA.

    Can anyone help me out while support thinks this over?

    Case#: 664188
    This is a cached copy. Click here to see the original post.

  • #8601

    longlam

    RE: Category field missing from contacts view (ODBC)

    Isn’t it CATEGORY_0? Using the old odbc connection v5.5.

  • #8602

    mark petzold

    I don’t think it is. CATEGORY_0 returns values like Customer, Vendor, etc. That seems to be the record type. I’m looking for the field called Category. It’s in the help documentation so it should be there, no?

    I should qualify that by saying that the pop-up help for that field in the UI says:

    To add choices to this list, go to Setup > Sales Force Automation > CRM Lists > New > Customer Category.

    That is incorrect (at least in our case). I finally found it in … crud, can’t find it again. Where was that?

    Edit: There it is! Setup > Accounting > Account Lists

    Still gone from Enterprise reporting views though. This is an urgent matter for us. I have just a few days to finalize this report and support doesn’t seem to understand the problem.

  • #8603

    longlam

    RE: Category field missing from contacts view (ODBC)

    Sorry, I wasn’t looking to closely. Try CUSTOMER_TYPE_ID and join to Customer_Type table and pull out the name column.

  • #8604

    mark petzold

    RE: Category field missing from contacts view (ODBC)

    I stand corrected. Support did find the answer (sorry Barry). The field has been moved (apparently) to a seperate table. The field on the customer table is customer_type_id. This is the link to the CUSTOMER_TYPES table.

    Adding it to my report causes a “failed to open rowet” error. It never ends

    I hope the documentation issues get fixed asap. It would have saved me hours of work and a call to support if only the help docs were kept up-to-date.

    PS: looks like you beat them longlam! Thanks for your help on this

You must be logged in to reply to this topic.