New answers tagged

1

Journey Builder processes records destined for your application on a row by row basis. You get one execute request per contact.


1

There could be several ways to automate sobject creation, if we need to create multiple custom objects. If you use SFDX, it is possible to use shane plugin to create custom object metadata file and then deploy those files or create a package from them and install the package. upperlim=2000 for ((i=0; i<=upperlim; i++)); do echo "$i" sfdx ...


1

The easiest way to do this is to use SFDX/VSCode (or some other similar tool that interfaces with the Metadata API). Once you have everything set up, you'll be able to pull down your org's Metadata. Then it should be as simple as CTRL/CMD-F to see if the template name is referenced in any files.


0

The formula would simply be First_Name__c & ' ' & Last_Name__c. When you use the = operator, you're converting this formula to a Boolean condition, which is not what you intended.


0

Custom metadata is considered as metadata due to which the DML Operations cannot be performed on Custom Metadata Type. Each change triggering a record creation is treated as a deployment. Please refer below link for more details. https://developer.salesforce.com/docs/atlas.en-us.apexref.meta/apexref/apex_class_Metadata_Operations.htm#...


0

Thankfully this is possible in Lightning Experience and Lightning App Builder, since we can include Related Lists from Parent Records. In the following example, I'm displaying the Contacts Related List from the Parent Account on the Opportunity Lightning Record Page. As long as the EmployeeManagement__c has the same Parent Account as the EmployeeTicket__c ...


1

Related lists are generated based on the lookup fields. You can see the EmployeeTicketList on EmployeeProject__c because there is a direct relationship. What you are asking is not possible. You don't have a choice rather than building a custom component that does the filtering and fetch ing based on the filtering criteria. Something like a LWC Component ...


6

They are created consecutively, not randomly, per salesforce instance (e.g. na3 will have its own pool of numbers). Within a single org, the ID values will never be duplicated, and even all throughout production, no Id will ever appear twice (because each ID also includes a "pod Id" to identify the origin of an Id). Cloning an org (e.g. a Sandbox) ...


Top 50 recent answers are included