[SalesForce] Display records based on multiple conditions

I have a list of records that I iterate over.

<aura:iteration items="{!v.items}" var=item">
    <aura:if isTrue="{!item.field__c == v.completed}">

        <c:item item="{!item}"/>

    </aura:if>
 </aura:iteration>

I have multiple conditions to display the data in different ways

Personal Items

Display current == true, personal == true of the ownerId == currentUserId (current personal items).
Display current == false, personal == true of the of the ownerId == currentUserId (completed personal items).

Shared records among the org

Display current == true, personal == false (current company items).
Display current == false, personal == false (completed company items).

I'm using a mix of conditional database calls, conditional css, and aura:if's. It's turning into a big mess making it all work together.

Are conditional database calls, conditional css, and aura:if's the only ways to control which records are shown?

If I embed multiple aura:if's it causes rendering errors with my lightning events.

Is there a best practice from Salesforce how to achieve what I'm trying to do?

Best Answer

Salesforce actually recommend using CSS if possible:

Use CSS to toggle markup visibility. You could use the tag to do the same thing but we recommend using CSS as it’s the more standard approach.

Reference here.

To use CSS, you can put something like this in your CSS file:

.THIS .hide {
  display:none!important;
}

And add the hide class where necessary.

<aura:iteration items="{!v.items}" var=item">
    <c:item item="{!item}" itemClass="{!item.field__c == v.completed ? hide : ''}"/>
</aura:iteration>

In the item component, you can then map itemClass to whatever class you need.

ie:

<aura:attribute name="itemClass" type="String"/>
<ui:outputText value="{!v.item}" class="{!v.itemClass}"/>

Related Solutions

[SalesForce] Multiple conditions on rendered attribute

I've been able to make things like this by simply doing this:

render="{!HasTeamMeber && ENT_ED_LIHTC__c.recordtype.name =='Standard Deal'}"

At least it seems to work fine with a page I was working on.

Another way would be to have a Boolean method in your controller that returns true or false and put the logic there.

[SalesForce] find duplicate records based on multiple fields

This could be base of your query for duplicates:

SELECT COUNT(Id), AccountId, OwnerId, ActivityDate
FROM Event
GROUP BY AccountId, OwnerId, ActivityDate
ORDER BY COUNT(Id) DESC
LIMIT 10

Don't run it yet! It's very likely to timeout and I can imagine it having serious performance issues.

This version is bit better (and it returns the earliest Event that matches the conditions):

SELECT MIN(Id) oldest, COUNT(Id), AccountId accId, OwnerId userId, ActivityDate d
FROM Event
WHERE AccountId != null AND ActivityDate = THIS_MONTH
GROUP BY AccountId, OwnerId, ActivityDate
HAVING COUNT(Id) > 1
ORDER BY COUNT(Id) DESC
LIMIT 10

Keep tweaking it till you're happy it can run in reasonable time. Make the WHERE clause selective, maybe increase the HAVING... The MIN(Id) is an idea for the "winner" record. Maybe you'll decide that newest one should win. Maybe you'll build something that asks the user to decide...

~~Anyway. Let's say that "earliest" Id will be a winner~~ (come to thing about it, we probably shouldn't count in Id's being sequential...).

So you have List<AggregateResult> which you can use to make the detailed query for all Events:

// Id oldestEvent = (Id) results[0].get('oldest');
Id accId = (Id) results[0].get('accId'), userId = (Id) results[0].get('userId');
DateTime actDate = (DateTime) results[0].get('d');

Use these to build SELECT ... FROM Event WHERE AccountId = :accId AND ... (optionally AND Id != oldestEvent if you want to skip my "winner". Or sort them by CreatedDate / ActivityDate DESC if you want to be sure the record you want is first in the result set.

The standard merge statement works only on Accounts, Contacts and Leads. I think you'll have to delete them with your own code, deciding which values to keep in the winner, which should just go... Luckily we can't make lookups to Events so at least you don't have to worry about relationships...

Best Answer

Related Solutions

[SalesForce] Multiple conditions on rendered attribute

[SalesForce] find duplicate records based on multiple fields

Related Topic