How do I create breakdown against a custom String field on the Task table?

[mikehotmail]

I have a custom field on the Task table called 'Business Unit'.   It is a simple String that is set via a business rule when the Task record it created.   I have a look-up table that is used to populate the field on the Task table.   I have an Incident Indicator that I want to add the breakdown.

How do I create a breakdown on a String field on the Task table?

[Arnoud Kooi]

You can find solutions on the community for this, but it's really recommended to sanitize your data.

In this case, probably define your BU's in a custom table and convert the string field to a Reference.

Check my blog on this topic:

Data preparation for a clean Breakdown.

[dhenslee]

Hey Arnoud,

I have the same/similar question as Mike.   I know what the best practice is but until my development can implement the best practice solution, Im still pushed to report on the data in place.   I can do similar things using the reporting module but it would be nice to know how to breakdown from a string field as its not as informative.   If you know where I can find information on 'breaking down based on a string field' in the community I would appreciate it.

Thanks!

[Arnoud Kooi]

There is actually one use case where it's ok and that is a breakdown on CI Class (sys_class_name), if you search for that, you should find it.

[Dennis R]

Oy... Arnoud is right.   In order to have a breakdown, you need to specify a breakdown source, which is a list of possible values.   A string by definition can be any value, so it will be extremely difficult to implement such a thing right now.   Just spitballing ideas, the only thing I could think of is to create a special table to hold the strings, and maybe periodically query your task table to add any new entries into it, and use that table as your breakdown source.   Or possibly write a script for your breakdown source that looks for the string in the special table, and if it doesn't find it, add it, then use its sys_id as the field to key off of for the breakdown.

But the "best practice" answer (as far as I can tell) is to change your field from a string to a reference to sys_choice or some other table, and store your possible values there.