#Lookup Relationships토론 중인 항목 2개

These symptoms — random missing Save button, broken lookup search, components loading unevenly, for one user in a large org — are almost always client-side, not Salesforce. Server-side problems hit everyone. Work it in this order: 

1) Open Salesforce in an Incognito/Private window (extensions off by default). If it behaves there, you've found it — a browser extension or corrupted cache. 

2) Disable browser extensions one at a time. Ad blockers, Grammarly, password managers and security/VPN extensions are the classic cause of missing Save buttons and dead lookup search — they inject into or block parts of the Lightning DOM. 

3) Clear cache and cookies for the Salesforce domain (a corrupted cached resource makes components load partially). 

4) Try the same login on a different browser or machine. If the trouble stays behind, it's the device/profile; if it follows the user, look at their account settings. 

5) Since it started Monday, check whether IT pushed a browser update, a new security extension, or a proxy/network change to that machine — a throttling proxy also explains the staggered loads and failed lookup searches. 

Start with the Incognito test — it isolates extension-vs-cache in about 30 seconds. 

if this helps, please mark it as the Best Answer so it helps the next person — thanks 🙂

Step 1: Create Lookup Relationship Field on Product 

Step 2: Apex Script to Create Leads and Products 

// Apex script to create Leads and Products and associate them

List<Lead> leadsToInsert = new List<Lead>{

    new Lead(LastName='Doe', Company='Doe Inc.'),

    new Lead(LastName='Smith', Company='Smith LLC'),

    new Lead(LastName='Johnson', Company='Johnson Corp.')

};

insert leadsToInsert; // Inserting the Leads

// Assuming the Leads are inserted and we have their IDs, create Products and associate them

List<Product2> productsToInsert = new List<Product2>{

    new Product2(Name='Product A', Related_Lead__c=leadsToInsert[0].Id),

    new Product2(Name='Product B', Related_Lead__c=leadsToInsert[0].Id),

    new Product2(Name='Product C', Related_Lead__c=leadsToInsert[1].Id),

    new Product2(Name='Product D', Related_Lead__c=leadsToInsert[1].Id),

    new Product2(Name='Product E', Related_Lead__c=leadsToInsert[2].Id)

};

insert productsToInsert; // Inserting the Products

@Rizwan Ahmad Noorie lookup field as such may not be natively supported in LWC exposed via mobile. as per link below

https://salesforce.stackexchange.com/questions/281191/why-doesnt-lightning-web-component-lookup-field-working-properly-on-mobile-brow

alternative would be to use lightning record picker component as per link below which is available inmobile

https://help.salesforce.com/s/articleView?id=release-notes.rn_lwc_record_picker_ga.htm&release=248&type=5

https://www.sfdcstop.com/2023/12/lwc-lookup-component-by-salesforce.html

Hey @Tom Rawling, I agree with Andrew.

You should use the just contact with no separate record types for different relationships.

You can use either picklist field as Andrew mentioned above or you can create a custom relationship object that will be related to the Contact object so that you can store the relationships there.

This model is already utilized by Non-profit Success Pack (in the non-profit space) and here is the entity diagram to see the relationship between those 2 objects:

https://architect.salesforce.com/1/asset/immutable/s/30bce1c/assets/images/data-models/nonprofit-success-pack-data-model.png

Hi Domenika,

The lookup should then be on Enrollment.

Think of it as a one-to-many. One being the Student and many being the enrollments since 1 student can have many enrollments against them

The many is always where the lookup goes, so you can now enter the name of the same (one) student on multiple (many) enrollments