0

The standard "Log a call" is:

enter image description here

I have a custom "Log a Call" button on Lead Object, This is de URL:

/00T/e?title=Call&who_id={!Lead.Id}&tsk5=Call&tsk4={!TODAY()}&RecordType=0123C000000a3kU&retURL=%2F{!Lead.Id}

enter image description here

but this creates a task of type task, not of type call.

enter image description here

How can you set the TaskSubtype=Call from the URL, without use followup? I already tried with variations of tsk5, tsk6, tsk7... tsk20 and it doesn't work

8
  • so tsk5=Call is the correct URL param. Is it possible you have automation on Task that changes Call to Task? Is Call a valid picklist value for Task.Type?. Are you sure you are looking at the OOTB field Task.Type on the UX and not some other field with the same label?
    – cropredy
    May 27, 2022 at 1:37
  • No, this happens in my environment and in a trailhead Playground like in the images, I know that tsk4 = Due Date, tsk6 = Comments, etc... but none of them set the TaskSubtype or the Type field (it should be tsk10=type but although set it, it's still a task you sybtype task and not call) May 28, 2022 at 5:18
  • Lightning or Classic?
    – cropredy
    May 28, 2022 at 5:20
  • Classic, this solution only works in Classic May 28, 2022 at 5:23
  • Have you done this? help.salesforce.com/s/articleView?id=000332230
    – cropredy
    May 28, 2022 at 5:29

1 Answer 1

1

Setting fields via URL hacking requires matching the URL param to the field's id (as defined in the HTML)

For Task.TaskSubtype, this can be seen by using your browser's developer tools:

<select id="TaskSubtype" name="TaskSubtype" tabindex="12">
    <option value="">--None--</option><option value="task">Task</option>
    <option value="email">Email</option>
    <option value="listEmail">List Email</option>
    <option value="cadence">Cadence</option>
    <option value="call">Call</option>
</select>

So, to set Task.TaskSubtype, your URL should look like this:

/00T/e?title=Call&who_id={!Lead.Id}&TaskSubtype=call
  &tsk5=Call&tsk4={!TODAY()}
  &RecordType=0123C000000a3kU&retURL=%2F{!Lead.Id}
  • URL parameter is case sensitive
  • URL param value should be the value of the desired <option>

I apologize for misreading your question and responding with &tsk5 as that is used for the Task.Type field

Most OOTB fields used in URL hacking (Classic) are the same as the field's API name, but for Task, we have these tski params which no doubt are for some long ago historical reason

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .