Displaying Account Closed and Account Open Cases On Case Page Layout

.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty margin-bottom:0;

up vote
1
down vote

favorite

I created a new case layout and I would like to display the related account's related cases. I can currently show all the related account's cases but I would like to split that up into two related lists one for open cases and the other for closed cases. Is there a way to do this using the app builder? If not, what's the best way to do this? We're currently using Classic but trying to switch to Lightning so I would need this to work in both.

asked 23 mins ago

Laura Bejjani

113

add a commentÂ |Â

up vote
1
down vote

favorite

asked 23 mins ago

Laura Bejjani

113

add a commentÂ |Â

up vote
1
down vote

favorite

asked 23 mins ago

Laura Bejjani

113

apex visualforce lightning-components visualforce-component app-builder

asked 23 mins ago

Laura Bejjani

113

asked 23 mins ago

Laura Bejjani

113

asked 23 mins ago

Laura Bejjani

113

asked 23 mins ago

Laura Bejjani

113

asked 23 mins ago

Laura Bejjani

113

add a commentÂ |Â

1 Answer
1

active

oldest

votes

up vote
2
down vote

There is an elegant solution to filter related lists declaratively. It's written up in full by Doug Ayers, but to summarize, it goes like this.

For each filtered category of Case you want to have, create a new lookup field on Case pointing to Account. Give each one an appropriate related list name, for example, Account_Closed__c, "Cases (Closed)".

Build a Process on the Case object that runs whenever the record is edited. In the Process, create a criteria node for each filtered category, and set the proper criteria on the node.

Add an action to each node to clear each of the filtered lookups other than its own, and copy the value of the native AccountId lookup to its own. So, for example, the criteria node for "Cases (Closed)" would have an action to clear the "Cases (Open)" lookup field, and populate the Account_Closed__c lookup with the value of the field AccountId.

Then, you can edit your Lightning record page in App Builder to include one or more Single Related List components and select the appropriate filtered related lists you just created.

answered 17 mins ago

David Reed

21.8k31640

im wondering if a lightning component would be easier (obviously it depends of the coding skills of the OP)
â€“Â glls
9 mins ago

It's really situation-dependent, I think. Lighting component would be a good solution given the coding skills. Given the asker's mention of App Builder and need for Lightning + Classic, I thought the declarative way might suit the bill so the native UI can be used.
â€“Â David Reed
6 mins ago

add a commentÂ |Â

Your Answer

StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "459"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);

);

draft saved

draft discarded

StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f236009%2fdisplaying-account-closed-and-account-open-cases-on-case-page-layout%23new-answer', 'question_page');

);

Post as a guest

Name

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

up vote
2
down vote

There is an elegant solution to filter related lists declaratively. It's written up in full by Doug Ayers, but to summarize, it goes like this.

For each filtered category of Case you want to have, create a new lookup field on Case pointing to Account. Give each one an appropriate related list name, for example, Account_Closed__c, "Cases (Closed)".

Build a Process on the Case object that runs whenever the record is edited. In the Process, create a criteria node for each filtered category, and set the proper criteria on the node.

Add an action to each node to clear each of the filtered lookups other than its own, and copy the value of the native AccountId lookup to its own. So, for example, the criteria node for "Cases (Closed)" would have an action to clear the "Cases (Open)" lookup field, and populate the Account_Closed__c lookup with the value of the field AccountId.

Then, you can edit your Lightning record page in App Builder to include one or more Single Related List components and select the appropriate filtered related lists you just created.

answered 17 mins ago

David Reed

21.8k31640

im wondering if a lightning component would be easier (obviously it depends of the coding skills of the OP)
â€“Â glls
9 mins ago

It's really situation-dependent, I think. Lighting component would be a good solution given the coding skills. Given the asker's mention of App Builder and need for Lightning + Classic, I thought the declarative way might suit the bill so the native UI can be used.
â€“Â David Reed
6 mins ago

add a commentÂ |Â

up vote
2
down vote

There is an elegant solution to filter related lists declaratively. It's written up in full by Doug Ayers, but to summarize, it goes like this.

For each filtered category of Case you want to have, create a new lookup field on Case pointing to Account. Give each one an appropriate related list name, for example, Account_Closed__c, "Cases (Closed)".

Build a Process on the Case object that runs whenever the record is edited. In the Process, create a criteria node for each filtered category, and set the proper criteria on the node.

Add an action to each node to clear each of the filtered lookups other than its own, and copy the value of the native AccountId lookup to its own. So, for example, the criteria node for "Cases (Closed)" would have an action to clear the "Cases (Open)" lookup field, and populate the Account_Closed__c lookup with the value of the field AccountId.

Then, you can edit your Lightning record page in App Builder to include one or more Single Related List components and select the appropriate filtered related lists you just created.

answered 17 mins ago

David Reed

21.8k31640

im wondering if a lightning component would be easier (obviously it depends of the coding skills of the OP)
â€“Â glls
9 mins ago

It's really situation-dependent, I think. Lighting component would be a good solution given the coding skills. Given the asker's mention of App Builder and need for Lightning + Classic, I thought the declarative way might suit the bill so the native UI can be used.
â€“Â David Reed
6 mins ago

add a commentÂ |Â

up vote
2
down vote

There is an elegant solution to filter related lists declaratively. It's written up in full by Doug Ayers, but to summarize, it goes like this.

For each filtered category of Case you want to have, create a new lookup field on Case pointing to Account. Give each one an appropriate related list name, for example, Account_Closed__c, "Cases (Closed)".

Build a Process on the Case object that runs whenever the record is edited. In the Process, create a criteria node for each filtered category, and set the proper criteria on the node.

Add an action to each node to clear each of the filtered lookups other than its own, and copy the value of the native AccountId lookup to its own. So, for example, the criteria node for "Cases (Closed)" would have an action to clear the "Cases (Open)" lookup field, and populate the Account_Closed__c lookup with the value of the field AccountId.

Then, you can edit your Lightning record page in App Builder to include one or more Single Related List components and select the appropriate filtered related lists you just created.

answered 17 mins ago

David Reed

21.8k31640

There is an elegant solution to filter related lists declaratively. It's written up in full by Doug Ayers, but to summarize, it goes like this.

For each filtered category of Case you want to have, create a new lookup field on Case pointing to Account. Give each one an appropriate related list name, for example, Account_Closed__c, "Cases (Closed)".

Build a Process on the Case object that runs whenever the record is edited. In the Process, create a criteria node for each filtered category, and set the proper criteria on the node.

Add an action to each node to clear each of the filtered lookups other than its own, and copy the value of the native AccountId lookup to its own. So, for example, the criteria node for "Cases (Closed)" would have an action to clear the "Cases (Open)" lookup field, and populate the Account_Closed__c lookup with the value of the field AccountId.

Then, you can edit your Lightning record page in App Builder to include one or more Single Related List components and select the appropriate filtered related lists you just created.

answered 17 mins ago

David Reed

21.8k31640

answered 17 mins ago

David Reed

21.8k31640

answered 17 mins ago

David Reed

21.8k31640

answered 17 mins ago

David Reed

21.8k31640

im wondering if a lightning component would be easier (obviously it depends of the coding skills of the OP)
â€“Â glls
9 mins ago

It's really situation-dependent, I think. Lighting component would be a good solution given the coding skills. Given the asker's mention of App Builder and need for Lightning + Classic, I thought the declarative way might suit the bill so the native UI can be used.
â€“Â David Reed
6 mins ago

add a commentÂ |Â

im wondering if a lightning component would be easier (obviously it depends of the coding skills of the OP)
â€“Â glls
9 mins ago

It's really situation-dependent, I think. Lighting component would be a good solution given the coding skills. Given the asker's mention of App Builder and need for Lightning + Classic, I thought the declarative way might suit the bill so the native UI can be used.
â€“Â David Reed
6 mins ago

im wondering if a lightning component would be easier (obviously it depends of the coding skills of the OP)
â€“Â glls
9 mins ago

It's really situation-dependent, I think. Lighting component would be a good solution given the coding skills. Given the asker's mention of App Builder and need for Lightning + Classic, I thought the declarative way might suit the bill so the native UI can be used.
â€“Â David Reed
6 mins ago

add a commentÂ |Â

draft saved

draft discarded

draft saved

draft discarded

Post as a guest

Name

Search This Blog

Iyfjky