Skip to main content

#NoCodeNovember0 personne en discute

Any tips/best practices to setup products where list price differs based on quantity?

-------------------------------------------------------------------------------------------------------------------------

Trying to setup products where the product list price would be different based on quantity. Don't see any standard features for products/pricebooks that support this so thinking I would have to setup a separate product for each quantity price point and then perhaps add validation to ensure the qty entered in the opp product is appropriate for the selected product price point.

11 commentaires
0/9000
Paul Foley a publié du contenu dans * APAC Success Central *

I've come across an issue with the Process Builder, when creating an Email Alert action.

When I try and create a new action it comes up with the following error message: You must specify a name for the action call.

 

I've noticed that there are a few other people with the same issue, but there doesn't seem to be a resolution to it yet.  https://success.salesforce.com/answers?id=9063A0000019Sv2QAE

 

Has anyone else come across this?

10 commentaires
0/9000

@Michelle Gillen Thank you for your blog - https://admin.salesforce.com/5-reasons-to-go-nocodenovember.  I was introduced to #Nocodenovember Group !! Looks like I will learn a lot just by exploring the posts!

0/9000
1 commentaire
0/9000

@The Blog Group @* Salesforce Administrators * @Solo Admins  @No Code November @Women in Tech 

@* Sales Cloud - Getting Started * @* Release Readiness Trailblazers * 

 

Make life simpler for your users by giving them the ability to assign a Salesforce record to themselves with a click of the button on the record detail page.

 

In support of #NoCodeNovember, for the entire month of November, there is a success community group (@No Code November) dedicated to finding creative ways to deliver features to customers without one line of code.

 

This is a use case solved by clicks instead of code in Salesforce Classic. (Note: This will not work in Lightning Experience.)

 

Hope you find it helpful.

-Jen

New Blog: Assign a Record to Me

0/9000

Selecting Opportunity Type when Converting Lead

 

I have created two different opportunity types (one for software and one for consulting) and I need to figure out how to be able to select a different opportunity type when converting a lead (and creating an opportunity). SFDC is automatically defaulting to one of the opportunity types. This seems like it would be a simple fix but I can't seem to figure out how to make this happen.

 

Thanks,

 

Erin

12 commentaires
  1. 24 nov. 2015, 13:59
    @Erin Olsen

    Create a custom picklist on the Lead object, call it "Lead Type" with values of "Software" and "Consulting". Map this field to a custom field "Lead Type" on the Opportunity, don't add to the page layouts. Map the Lead field to the Opportunity field. Create a Process to be fired only when an Opportunity is created. You'll need two Criteria:

    1. Criteria: "Lead Type" = "Software",

    Action: Update Record - Update Opportunity: Opportunity Record Type = id of the Software Recordtype.

    2. Criteria: "Lead Type" = "Consulting",

    Action: Update Record - Update Opportunity: Opportunity Record Type = id of the Consulting Recordtype.

    hth.

    Aiden

0/9000

We're about ready to rollout State and Country picklists in our org. I'm doing some final testing and noticed that when you set the default country, if that country has states, the user must complete then State is required too. Here's why this is a problem:

 

  1. We don't always have two addresses on file for our Accounts and Contacts; with US as the default, I'm required to fill-in a state for both.
  2. We have a record type for things like vendors, etc. that allows users to fill-in very little; address isn't required at all.
  3. If I turn off the default, I'm making my users search for US 9 times out of 10 when inputting an address, which doesn't seem like a good option either.

 

Has anyone else run into this and found a good workaround?

 

@* Salesforce Administrators * @Admin Group, Chicago, US @WIT Group, Chicago, US #NoCodeNovember #State And Country Picklist 

11 commentaires
  1. 23 nov. 2015, 17:43
    @Mike Creuzer

    We tested between our Salesforce sandboxes successfully. Our Marketo landing pages no longer use address information, but used to, so we tested that and it worked. We tested before and after switching the integration value to the ISO codes. I'm not sure if changing those would help your Pardot issue.

    The way we've built out validation rules, address is only required at a point our P&P require that they've gathered that info. Otherwise, it's optional.

0/9000

I'm hoping to accomplish this without code (especially since, as a non-coder, every month is #NoCodeNovember for me). I opened a Case with support, but their solution was Visualforce; I'm hoping the great minds out there might have a different solution.

 

I built Compliance object for our B2C business unit. The Compliance object has a master-detail relationship with Accounts. I've also built another object, Insiders, which connects Contacts and a table of publicly-traded companies (Securities). A Contact can have more than one Insider record. The majority of the time, the relevant Insider records belong to the related Account. The less common use case is a Contact from another Account might need to be linked to the Compliance record too (such as a trustee).

 

Here's what I'd like to accomplish:

  • I need to show the Contacts in an Account on the Compliance object and want to allow users to connect a Contact outside of that household. 
  • I need to show the Insider entries that each Contact attached to the Compliance record have.

 

Can I do this without code?

 

@Women in Tech @* Salesforce Administrators * @* Customer Success * 

12 commentaires
  1. 23 nov. 2015, 17:11
    @Ken CowanI haven't. I'm familiar with what it does, but that's about it. It's on my (long) list of things to try out in my sandbox. Can you give me a feel for how this might help in this instance? I ask because I have a similar project right behind this one.
0/9000

Here's the fourth in our series of Admin Commandments posted on the Salesforce Weekly blog.

 

This one tackles #NoCodeNovember but with a twist, arguing that a good admin should know the value of code even if they don't know code itself. 

 

And there's a special nod to the ability of #Process Builder to separate the when from the what, leaving admins in charge of when code runs even if they didn't write it.

 

Hope you enjoy it!

Admin Commandment #4 – An Awesome Admin should always… know the value of clicks AND code!

5 commentaires
0/9000
0/9000