'Assigned to' fields not working

[droat]

When I am in studio and I bring either of the 'Assigned to' fields over to any of the layouts, they don't work. I have noticed that after I save a layout that the tooltip that shows where the output will go disappears. For example: the 'Assigned to User' label is accompanied by the actual field 'ASSIGNED_USER_LINK', until I save. Then the field is gone but the label remains.

Version 4.5.1b
Apache
MySQL 4.1.21

[kbrill]

This is a known bug and I think it has been fixed in the next version. In 451e you will have to manually edit the HTML to put the field back on the view or restore a fresh copy of the html and do your customizations again.

[droat]

What code would I modify?

[kbrill]

The EditView.html file in the modules directory

[droat]

thank you for your quick responses.

I found the EditView.html in the Leads subdirectory of Modules. But it shows the full field there already. Here is the code:

<td class="dataLabel"><span sugar='slot8'>{APP.LBL_ASSIGNED_TO}</span sugar='slot'></td>

and here is the code from DetailView.html

<td valign="top" class="tabDetailViewDF"><span sugar='slot22b'>{ASSIGNED_USER_NAME}</span sugar='slot'></td>

Thanks again

[kbrill]

Thats not the full code, this is:

<td class="dataLabel"><span sugar='slot19'>{APP.LBL_ASSIGNED_TO}</span sugar='slot'></td>
<td class="dataField"><span sugar='slot19b'><input class="sqsEnabled" tabindex="1" autocomplete="off" id="assigned_user_name" name='assigned_user_name' type="text" value="{ASSIGNED_USER_NAME}"><input id='assigned_user_id' name='assigned_user_id' type="hidden" value="{ASSIGNED_USER_ID}" />
<input title="{APP.LBL_SELECT_BUTTON_TITLE}" accessKey="{APP.LBL_SELECT_BUTTON_KEY}" type="button" tabindex='1' class="button" value='{APP.LBL_SELECT_BUTTON_LABEL}' name=btn1
onclick='open_popup("Users", 600, 400, "", true, false, {encoded_users_popup_request_data});' /></span sugar='slot'>
</td>

Notice the hidden field and the select button

[faredgetechnology]

Hi,

Thanks for the fix above. It correctly fixes the EditView page, but I can't get the DetailView page working correctly.

Currently it has:
<td class="tabDetailViewDL"><span sugar='slot5'>{APP.LBL_ASSIGNED_TO_USER}</span sugar='slot'></td>
<td class="tabDetailViewDF"><span sugar='slot5b'>{ASSIGNED_USER_NAME}</span sugar='slot'></td>

I've tried other variations on the theme using:

tabDetailViewDL = APP.LBL_ASSIGNED_TO_USER (OK)
tabDetailViewDL = APP.LBL_ASSIGNED_TO (OK)
tabDetailViewDL = MOD.LBL_ASSIGNED_TO_USER (not visible)

and:
tabDetailViewDF = ASSIGNED_USER_NAME (not visible)
tabDetailViewDF = ASSIGNED_USER_ID (not visible)
tabDetailViewDF = ASSIGNED_TO_USER (not visible)
tabDetailViewDF = ASSIGNED_USER_LINK (not visible)

as well as pasting the same control as for the EditView:

<td class="tabDetailViewDL"><span sugar='slot3'>{APP.LBL_ASSIGNED_TO}</span sugar='slot'></td>
<td class="tabDetailViewDF"><span sugar='slot3b'><input class="sqsEnabled" tabindex="1" autocomplete="off" id="assigned_user_name" name='assigned_user_name' type="text" value="{ASSIGNED_USER_NAME}"><input id='assigned_user_id' name='assigned_user_id' type="hidden" value="{ASSIGNED_USER_ID}" />
<input title="{APP.LBL_SELECT_BUTTON_TITLE}" accessKey="{APP.LBL_SELECT_BUTTON_KEY}" type="button" tabindex='1' class="button" value='{APP.LBL_SELECT_BUTTON_LABEL}' name=btn1 onclick='open_popup("Users", 600, 400, "", true, false, {encoded_users_popup_request_data});' /></span sugar='slot'>
</td>

Which returns a blank box & select button.

I had a look at other examples in the same file that do work:

<td valign="top" class="tabDetailViewDL" colspan="1"><span sugar='slot45'>{MOD.LBL_ACCOUNT_NAME}</span sugar='slot'></td>
<td valign="top" class="tabDetailViewDF" colspan="1"><span sugar='slot45b'>{ACCOUNT_NAME}&nbsp;</span sugar='slot'></td>

and can't see any substantive difference. If I use the variable "ACCOUNT_NAME" instead of "ASSIGNED_USER_NAME" (or any variations on the theme) I get the account name correctly appearing.

So... I'm guessing that I'm either using the wrong thing to reference the piece of data I'm after - if this is the case, then why isn't it consistent with the EditView page which displays ASSIGNED_USER_NAME and stores ASSIGNED_USER_ID? Do I need to give it some context?

In the DetailView.html file for Opportunities it uses the value "ASSIGNED_USER_LINK" which I've tried as well to no avail. (it works in the Opportunities view however).

Sorry I'm a bit of a newbie at this - I've never delved into customising Sugar Forms before so hopefully this isn't too obvious!

We're running SugarCRM OpenSource 4.5.1h (build 1104) on Apache 2.0.53/PHP 4.3.11 / MySQL 4.1.15. Client is WinXP Pro / Firefox 2. Doing the html edits using vi obviously.

Thanks,

Chris

[cshort@medicat.com]

I was having the same problem you were... and I just figured it out.

I was working in the Bugs module but it's probably the same for you.

In the detailView.PHP the username is being defined as:

$xtpl->assign("ASSIGNED_TO", $focus->assigned_user_name);

and yet when you edit it in Studio the field it wants to create looks like this:

<td class="tabDetailViewDF"><span sugar='slot4b'>{ASSIGNED_USER_NAME}</span sugar='slot'></td>

I simply edited that line and changed {ASSIGNED_USER_NAME} to {ASSIGNED_TO} and it showed right up. Sloppy coding.

Here's the line I put that fixed it.

<td class="tabDetailViewDF"><span sugar='slot6b'>{ASSIGNED_TO}</span sugar='slot'></td>

Good luck.
-Chris

[faredgetechnology]

Awesome - fixed! Thankyou very much Kenneth & Chris!