Hi,
Could someone let me know ?
1. what are scenarios where we can use ?
a!recordActionItem()
2. Why do we need to define the default value while adding a row using Add Row link?
is it mandatory?
addRowlink: a!dynamicLink( label: "Add Employee", value: { startDate: today() + 1 }, saveInto: { a!save(local!employees, append(local!employees, save!value)) } ) ) }3. In what scenario/s we will go for Editable GridThanksFaisal
Discussion posts and replies are publicly visible
1. a!recordActionItem() can be used within a!gridField() or a!recordActionField() on any interface for taking action against your records. The common related action scenarios would be updating, deleting, or escalating. Let's say you had a record called 'Employees' and a list action called 'Add Employee'. You could put that action on any interface you want using a!recordActionItem()
2. addRowLink does not require a default value, you can leave it blank.
3. You should use an editable grid when your use case requires users to edit data per row inline instead of opening a larger action.
Thank you so much Danny for your explanation. I will try part 1 first.
Hi Danny,
One thing I missed to query.
Whether it is a!recordActionItem() and a!recordActionField() do we have to mandatorily use data source as recordtype or we can use them in case the data source is DS Entity ?
Thanks
Faisal
I think my query was wrong. It will be only Record Type as DATA source as actions are configured on record Type.
Yes just to confirm - you must use a record type as the source of a record action (although that record type can reference a data store entity).