|
The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
Forum to discuss SalesLogix legacy development including views, scripts, etc.. View the code of conduct for posting guidelines.
|
|
|
|
Literals in Support Groups
Posted: 29 Mar 06 3:21 PM
|
fiogf49gjkf0d Ryan,
We read your article at http://saleslogixblog.com/rfarley/archive/2004/09/01/996.aspx and it helped a lot. However, we had a couple questions:
In regards to:
:accountownerlist
:pluginownerlist
:ticketassignlist
:defectownerlist
:defectassignlist
What do they mean? Are they everyone who owns an account, plugin, everyone that can be assigned a ticket, etc?
ALso, we have a support group where it will not allow us to use :UserID but will allow :TicketAssignList. Any ideas?
Thanks,
Paul |
|
|
|
Re: Literals in Support Groups
Posted: 12 Apr 06 5:39 PM
|
fiogf49gjkf0d Hi Paul,
To be honest, I never use support. I've never liked it 
So I can't say I've used those literals for quite some time and I really can't remember much about them. IIRC there are OOTB groups in support that use them. If that is the case you should be able to edit these groups and see how they are used in those groups at least. |
|
|
|
Re: Literals in Support Groups
Posted: 17 Apr 06 5:21 PM
|
fiogf49gjkf0d ticketassignlist is actually used in the My Ticket group of the Ticket section of the sales client (6.2 introduced it I think?), since it came from the support side. I made the mistake of trying to use :userid or something stupid like that and it didn't work.
Here's the SQL shown from the Profiler:
SELECT A1.TICKETID, A1.TICKETNUMBER, A2.ACCOUNT A2_ACCOUNT, A3.NAMELF A3_NAMELF, A3.WORKPHONE A3_WORKPHONE, A1.STATUSCODE, A4.DESCRIPTION A4_DESCRIPTION, A1.RECEIVEDDATE, A1.NEEDEDBYDATE, A1.MODIFYDATE, A1.ASSIGNEDTOID, A1.AREA FROM TICKET A1 LEFT OUTER JOIN PICKLIST A5 ON (A1.STATUSCODE=A5.ITEMID) LEFT OUTER JOIN URGENCY A4 ON (A1.URGENCYID=A4.URGENCYID) LEFT OUTER JOIN CONTACT A3 ON (A1.CONTACTID=A3.CONTACTID) LEFT OUTER JOIN ACCOUNT A2 ON (A1.ACCOUNTID=A2.ACCOUNTID) WHERE NOT (UPPER(A5.TEXT) LIKE 'CLOSED%') AND (A1.ASSIGNEDTOID IN (?))
A couple of lines later it has this statement which apparently is what is returned to the client:
SELECT A1.TICKETID, (isNull(A1.ALTERNATEKEYPREFIX,'') + '-' + isNull(A1.ALTERNATEKEYSUFFIX,'')), A2.ACCOUNT A2_ACCOUNT, (isNull(A3.LastName,'') + ', ' + isNull(A3.FirstName,'')) A3_NAMELF, A3.WORKPHONE A3_WORKPHONE, A1.STATUSCODE, A4.DESCRIPTION A4_DESCRIPTION, A1.RECEIVEDDATE, A1.NEEDEDBYDATE, A1.MODIFYDATE, A1.ASSIGNEDTOID, A1.AREA FROM TICKET A1 LEFT OUTER JOIN PICKLIST A5 ON (A1.STATUSCODE=A5.ITEMID) LEFT OUTER JOIN URGENCY A4 ON (A1.URGENCYID=A4.URGENCYID) LEFT OUTER JOIN CONTACT A3 ON (A1.CONTACTID=A3.CONTACTID) LEFT OUTER JOIN ACCOUNT A2 ON (A1.ACCOUNTID=A2.ACCOUNTID) WHERE A1.TICKETID IN ('t6UJ9A000004','t6UJ9A000007','t6UJ9A00000B')
I suspect the other literals do something similar though I'm too lazy to try them all out. The profiler groups 4 statements together in the SQL Log so they shouldn't be hard to pinpoint. You typically go with the first one to see what starts the ball rolling and the last one is what the client uses to return to the user. I think some of this seems hardcoded which is probably why my SQL wasn't returning correct results. Enter the SLX Profiler to save the day I guess. Hopefully "technology preview" is shorthand for "better be included soon". |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|