eservice - link to account automatically

Mar 5, 2009 at 6:45 PM
hi there,

when a contact creates a new case it is linked to the contact rather than the account.

Is there any easy way of changing this so that the related account is there by default?

we also use the responsiblecontactid field by default, but this isnt populated?

thanks,

Dan
May 27, 2009 at 2:48 PM

Dan - Did you figure out how to do this? I'd like to do the same thing.

We use the responsible contact field as well. 

May 27, 2009 at 2:51 PM

sorry i didnt.

the c360 portal is an alternative.

 

Dan

May 27, 2009 at 10:01 PM

Hey,

I was able to figure this out finally.

I was running into the same issue when a case was being created in CRM it was being assigned to the Contact rather than the Account associated with that contact.

What I did was modified the New Case created via the portal workflow

Removed the email to customer and modified the update the case origen = web

In properties of the web form I modified these below with these dynamic vaules.

On the customer setting (Parent Customer(Customer(contact)))

On Responsible Contact (Customer(Case))

When the workflow fires it checks to make sure that the case is created via the web user only and then it should fire the update step and make the correct modifications.

Dorey 

Jun 1, 2009 at 10:16 PM

Thanks Dorey! That worked.

Jul 16, 2009 at 12:05 PM

hi there,

we've just migrated away from c360 product.  just to confirm this worked for me.

i didnt delete the email section (although i may need to - still testing)

i couldnt find those exact settings so i used:

customer setting: {account(customer(contact))}

responsible contact:{contact(customer(contact))}

 

from my experiences as well for reference:

1. the url for signup never works - i used the url builder plugin provided in a separate msdn blog post (for formatting ntext fields as html) - works perfectly now

2. using frontpage extensions and visual studio massively speeds up customization of the portal which is otherwise a scary proposition

3. user management is done via visual studio (open website - has to be on the local machine) -> website -> ASP.NET configuration

this allows configuration of roles.

it is then possible to configure group permissions on the site e.g. intranet.

there is a remote asp.net 2.0 tool for managing users which is really handy (im not connected to them in any way)!

http://www.qualitydata.com/products/aspnet-membership/