a!recordLink or a!urlForRecord with parameters for Record Views?

Question

Hi All, 
 I have an interesting use case where the client wishes to open a 'Task' within a 'Case'. 
 For Context, we have a design where our Case has a one-to-many relationship with Tasks. 
 We have a 'Tasks' View on the Case record which has a selectable a!gridField where the end user can select a Task from the grid. This populates a Task screen below with data and record actions for the selected Task. 
 The client would like to navigate to the Case record -> Tasks View via both the a!recordLink() and a!urlForRecord() with the Task already pre-selected in the UI. 
 The client is not willing to have the link navigate to a Task Record as they find it confusing and do not want the User to leave the top level Case Record. 
 Is there any workaround I can use or is linking to a Task Record directly the only option available? 
 Many Thanks for your time, 
 Zac

Shanmathi Ponnusamy · Answer

Yes passing parameters is not supported in the record views. I would suggest to go with your second approach since the client wants to Navigate to record.

Soma · Answer

The maximum you would be able to drill down inside a record using urlForRecord() is till the views of the record. So, your case is not possible using urlForRecord(). 
 Your second option may introduce maintainability issues. So, like you I am not fond of it too. 
 I suggest two options here: 
 1. Create a new interface that mimics the task view of the record that can have rule inputs and call it by passing the inputs using urlforsite() 
 2. Convince the client that there is no direct way to do it.

a!recordLink or a!urlForRecord with parameters for Record Views?

Top Replies