Add Account column to MyOpenTasks dashlet?

[spectheintro]

Is it possible to add an Account column to the MyOpenTasks dashlet on the Home page? It does not seem to be a selectable option, and a quick look at the code shows that no labels for "Account" exist in the module. In EditView you can create a relationship with an Account, but it seems to be a unique sort of relationship that uses "parent_type" tags as opposed to the standard arrays. Can anyone shed some light on this problem? I just want users to be able to see what Accounts their Open Tasks correspond to, on their home page. Thanks!

[Angel]

Here is an idea I used before which might help you too...

1. Create a custom field in the Tasks module, define it as though it were the Name field from the Accounts module.
2. Create a logic hook that stores the corresponding Account name in the custom field when a Task is edited/saved.
3. Select the custom field in the Dashlet.

[spectheintro]

2. Create a logic hook that stores the corresponding Account name in the custom field when a Task is edited/saved.

Could you shed some more light on this? Does this require creating a relationship to do? I have the account_id (because it is stored in parent_id) but there's no relationship from which to pull the associated account_name. Is there a simpler way to do it than what I described?

[Angel]

Since you have the Account ID, you can use the logic hook to execute the query:

SELECT name FROM accounts WHERE id = '%id%'

That would give you the name and you can do whatever you want with it at that point.

As far as there being an easier way, this the easiest way that I could find. Maybe others have a simpler solution.

[spectheintro]

Ok, I'm following you, but I'm not sure how to store that query in a custom field so that I could then call it by (for example) "account_name". Would I tweak the custom field in vardefs or in field arrays? I know how to display a query in a sugar slot, but I'm lost when it comes to storing queries in custom fields.

Thank you so much for your responses.

[Angel]

The query is contained within your custom code in the logic hook. You are not storing it in a field anywhere in the database. It is just custom PHP that gets triggered automatically by Sugar when you "Save" a Task.

The field itself is defined via the Studio and you don't have to mess with any Sugar PHP files. Everything would be upgrade safe.

Check out the Wiki entry on logic hooks for some more insight:
http://www.sugarcrm.com/wiki/index.p...l_custom_logic

[spectheintro]

Ok, great; I'll take a look at that tonight/tomorrow and will hopefully be able to crack it.

Thanks again! I really appreciate your responses.