777-salesforce

20250508-777-prompt-salesforce

Schema Builder can make you directly adding attribute into the object(customized object)

gui, mindmap
view object manager right click as well (feature)
but you still to make it manually make it visible for user , by drag and drop , kind of like make __object to
there is another visible setting require to make (field setting) , user + field visible → really visible in profile
use Fields & Relationships to check the basic unit / attribute for understanding

using gpt to suggesting which field do we need to create

e.g. Fields: Warranty Name, Description, Warranty Provider, Start Date, End Date, Warranty Status, Asset.

Q:For the Warranty Management Object, tell me more about the Warranty Provider field. Could that Warranty Provider field be related to the Account object? If so, should I make that a Lookup Relationship or a Master-Detail Relationship?

master-detail relationship → mean that child object need their parent object created first

Q:For the Warranty Status field, should that be a picklist field? And if so, what are 4 or 5 good example status designations that | should include as options?

in sales force you cant’ create master detail relationship field if you have alread created records(like contact,(phone, address , email)), you need to created look up and then flip it to be master detail relationship
- not adding related list in this case
in view mode , selet new created field , pick existed contact and apply to all view list unit

once you apply to previous data, now you can flip it to master detail relationship

enable re-parenting, (like change the contact)

now adding to it to page layout(front end) by using Lightning App Builder → details → contact layout → it will jump to object manager page layout

adding more features on that (more info)
adding to not only contact page , but also account page (repeated adding frontend like notion page)

Junction objects

allow you create many many relationship

Q: apply to our case , what can be ^^ in our case: mulitiple contact that responsible for different roles → junction objects

it created from backend and make it visable in the graph

bulking add roles from gpt in setup →object manager

and change the data type from text to auto number
- so there isn’t text need to be input , but auto number instead

the usage :

more detail can be picked as junction objects did that

when deleting the field, affecting:

page layout
automation
reporting

make sure to do data export , backup first, better checked in mindmap as well

record types

objects are nouns, record types is adj

it will increased add a level or layer of complexity.

vendor, clinet , provider etc

you can created different page layout for different type of record types

there is affect on enabling visible for both record types accounts

master account (prospect account, default maybe → showing how many profit)

make default optin page also same as above

that is why he is leaving a blink option above section

mind map for complex cases

now he change the correct name, so previous setup is easy for he locating which page

not giving purchase list in previous section so that now not allowing to pick that

controling pick list and page layout, micro management ?

it auto as New Account: Warranty Provider, as he only got one record type

changing current non- warranty provider to warraty provider

adding record type in front end

account page → front end again

adding warranty page look up list

warranty page → edit object → field & relationship → add look up → option

asking gpt for useful formula

Sales

campaign Hierarchy

responeses

analysis on effectivness and return of investment
custom links → view capagin influence report

open leads → potential customer ?

creation leads

Once a Lead is qualified, it can be converted into an account, contact, and Opportunity record in Salesforce, allowing sales reps to continue track managing the customer relationship as it progresses through the sales pipeline.